[Group.of.nepali.translators] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table

2021-09-10 Thread AceLan Kao 
** Also affects: linux-oem-5.10 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
   Status: New => Invalid

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

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

Title:
  Support importing mokx keys into revocation list from the mok table

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-oem-5.10 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]

   * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
  which revokes many Ubuntu kernel hashes and 2012 signing key.

   * Kernel should import those into it's %:.blacklist keyring such that
  it prohibits signed kexec of the revoked kernels.

   * v5.13-rc1 kernel has learned how to import mokx and how to import
  full certs into the %:.blacklist keyring.

   * However, it only does so by reading MokListXRT efi variable.

   * Due to the large size of Ubuntu's vendor-dbx, shim does not create
  MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2
  MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also
  exposes MokListXRT via mokvar table, which is easier to parse and
  contains all the revocations in full. Kernel needs a patch to read
  MokListXRT via mokvar table.

   * We have two options on how to proceed from here, either we include
  the same hashes and certs as our vendordbx in in the kernel as
  revocation list, or we fix kernel to read MokListXRT via mokvar table

   * The above is known as CVE-2020-26541

   * Separately it would be nice to add informational dmesg messages
  when revoking signing certificates, as a good indication that signing
  key rotation events have happened and have been applied correctly.

  [Test Plan]

   * Boot kernel with 15.4 based Ubuntu shim

   * Install keyutils package

   * Execute $ sudo keyctl list %:.blacklist it should list in exccess
  of 300+ hash entries. It also must list assymetric Canonical signing
  key from 2012.

   * Separately check dmesg to observe that asymmetric canonical signing
  key from 2012 is revoked.

  [Where problems could occur]

   * EFI variable storage can be full thus preventing shim to mirror
  efivars and the moktable. On decent hardware this should not happen,
  but has been observed to be corrupted on some older EDKII based OVMF
  instances with small EFI variable storage space (pre-4MB).

  [Other Info]
   
   * The patches to fix the above have been submitted upstream

  
https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/

  
https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/

  This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE
  kernel, until accepted upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+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 1932029] Re: Support builtin revoked certificates

2021-09-10 Thread AceLan Kao 
** Also affects: linux-oem-5.10 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
   Status: New => Invalid

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

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

Title:
  Support builtin revoked certificates

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-oem-5.10 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  Upstream linux kernel now supports configuring built-in revoked
  certificates for the .blacklist keyring.

  Add support in our kernel configuration to have built-in revoked
  certificates.

  Revoke UEFI amd64 & arm64 2012 signing certificate.

  Under UEFI Secureboot with lockdown, shim may attempt to communicate
  revoked certificates to the kernel and depending on how good EFI
  firmware is, this may or may not succeed.

  By having these built-in, it will be prohibited to kexec file_load
  older kernels that were signed with now revoked certificates, however
  one boots.

  [Test Plan]

   * Boot kernel directly, or just with grub, and without shim

   * Check that

  $ sudo keyctl list %:.blacklist

  Contains assymetric 2012 key.

  [Where problems could occur]

   * Derivative and per-arch kernels may need to revoke different keys,
  thus this should be evaluated on per arch & flavour basis as to which
  keys to revoke.

  [Other Info]

   * In theory, this only needs to be revoked on amd64 and arm64, but
  empty revocation list is not allowed by the kernel configury, thus at
  the moment revoking 2012 UEFI cert for all architectures.

   * an ubuntu kernel team regression test is being added to assert that 
expected revoked certificates have been revoked
  see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+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 1884159] Re: Update lockdown patches

2020-07-06 Thread AceLan Kao 
** Also affects: linux-oem-osp1 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-oem-osp1 (Ubuntu Xenial)

** No longer affects: linux-oem-osp1 (Ubuntu Eoan)

** No longer affects: linux-oem-osp1 (Ubuntu Focal)

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

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   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/1884159

Title:
  Update lockdown patches

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  Impact: The lockdown patches have evolved over time, and part of this
  was restricting more areas of the kernel. Not all of these additions
  were backported, and some can lead to lockdown bypasses, see [1] and
  [2].

  Fix: Backport newer lockdown restrictions to older releases.

  Test Case: Test cases for most of the backports can be found at [3],
  and [4] is another test case. Some which need e.g. specific hardware
  to test have not been tested.

  Regression Potential: Most of these are small, simple fixes with low
  potential for regression. Users may also lose access to some
  functionality previously accissible under secure boot. Some changes
  are more substantial, especially the hw_param and debugfs changes for
  xenial, but they are based on well-tested upstream code. The xmon
  backports also carry a more moderate risk of regression.

  [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html
  [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/
  [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests
  [4] 
https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884159/+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 1861238] Re: Root can lift kernel lockdown via USB/IP

2020-02-25 Thread AceLan Kao 
** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-oem (Ubuntu Xenial)

** No longer affects: linux-oem (Ubuntu Disco)

** No longer affects: linux-oem (Ubuntu Eoan)

** No longer affects: linux-oem (Ubuntu Focal)

** Changed in: linux-oem (Ubuntu Bionic)
   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/1861238

Title:
  Root can lift kernel lockdown via USB/IP

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]

  It's possible to turn off kernel lockdown by emulating a USB keyboard
  via USB/IP and sending an Alt+SysRq+X key combination through it.

  Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and
  CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules
  provided in the linux-extra-modules-* package.

  See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip

  [Test Case]

  $ git clone https://github.com/xairy/unlockdown.git
  $ cd unlockdown/01-usbip/
  $ sudo ./run.sh
  $ dmesg

  # Ensure there are no log entries talking about lifting lockdown:
  sysrq: SysRq : Disabling Secure Boot restrictions
  Lifting lockdown

  # You should see a SysRq help log entry because the Alt+SysRq+X
  # combination should be disabled
  sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) 
memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) 
show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) 
poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) 
show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) 
dump-ftrace-buffer(z)

  [Regression Potential]

  Some users may see a usability regression due to the Lockdown lift
  sysrq combination being removed. Some users are known to disable
  lockdown, using the sysrq combination, in order to perform some
  "dangerous" operation such as writing to an MSR. It is believed that
  this is a small number of users but it is impossible to know for sure.

  Users that rely on this functionality may need to permanently disable
  secure boot using 'mokutil --disable-validation'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861238/+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 1774387] Re: inotify07 in LTP syscall test failed with X/X-LTS/A kernel

2019-09-16 Thread AceLan Kao 
This bug was nominated against a series that is no longer supported, ie
artful. The bug task representing the artful nomination is being closed
as Won't Fix.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  inotify07 in LTP syscall test failed with X/X-LTS/A kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Artful:
  Won't Fix

Bug description:
  The "inotify07" from the LTP syscall tests have failed on a testing
  node with X-LTS i386 kernel installed.

  <<>>
  tag=inotify07 stime=1527762360
  cmdline="inotify07"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  inotify07.c:206: INFO: ovl/test_dir ino=27918358
  inotify07.c:216: INFO: ovl/test_dir ino=27918358
  inotify07.c:157: FAIL: didn't get event: mask=4004
  inotify07.c:157: FAIL: didn't get event: mask=0020
  inotify07.c:157: FAIL: didn't get event: mask=0008
  inotify07.c:157: FAIL: didn't get event: mask=0004

  Summary:
  passed   0
  failed   4
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=37
  <<>>

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-127-generic 4.4.0-127.153~14.04.1
  ProcVersionSignature: User Name 4.4.0-127.153~14.04.1-generic 4.4.128
  Uname: Linux 4.4.0-127-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Thu May 31 10:19:30 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774387/+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 1720977] Re: [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang

2019-07-29 Thread AceLan Kao 
** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang

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

Bug description:
  [Impact]
  There is a USB Ethernet port, 0bda:8153, on Dell IE Docking.
  After plugged in the docking, system hard hangs.

  [Fix]
  This issue has been fix after v4.11-rc4, so after bisecting the kernel, we 
found the first bad commit, and realized this issue is from Realtek USB 
Ethernet driver with a non-initialized list.
 98d068a r8152: fix the list rx_done may be used without initialization

  [Test Case]
  Verified on the Dell XPS and IE docking, and confirm this patch works.

  [Regression Potential]
  It's a one line patch and do the initialization of the list variable, there 
should be no any regression would be resulted from this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1720977/+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 1692836] Re: Dell XPS 9360 wifi 5G performance is poor

2019-07-29 Thread AceLan Kao 
** Changed in: linux (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/1692836

Title:
  Dell XPS 9360 wifi 5G performance is poor

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

Bug description:
  TX throughput is not good in Ubuntu in IEEE 802.11ac mode.

  Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu
  Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and 
Tx 62MBit/s using the same hardware setup.
  Same result with WPA2 disabled in unencrypted mode.

  Steps to Reproduce:
  1. connect to Wifi
  2. copy a large file from XPS 13 to a share on a 2nd system

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1692836/+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 1708372] Re: The Precision Touchpad(PTP) button sends incorrect event code

2019-07-29 Thread AceLan Kao 
** Changed in: linux (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/1708372

Title:
  The Precision Touchpad(PTP) button sends incorrect event code

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:
  [Impact]
  The touchpad right button should send 273(BTN_RIGHT),
  and the left button should send 272(BTN_LEFT)
  But the touchpad right button sends 274(BTN_MIDDLE),
  and the left button sends 273 (BTN_RIGHT)

  [Fix]
  The fix is pretty simple to just decrease the event code by 1.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  The patch has strict if statement, so it won't affect other touchpad devices.
  And no more rework on this code snip after this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1708372/+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 1693393] Re: Power consumption issue on suspend-to-idle(s2idle)

2019-07-29 Thread AceLan Kao 
** Changed in: hwe-next
   Status: In Progress => Fix Released

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

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

Title:
  Power consumption issue on suspend-to-idle(s2idle)

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:
  The power consumption is pretty high(8Watt) during suspend-to-idle
  mode under Xenial.

  1. It consumes 8Watt under 4.4 kernel
  2. It consumes 4Watt under 4.8 kernel
  3. It consumes 2Watt under 4.11 kernel

  There are essential patches in 4.8 and 4.11 kernels, they are
  In 4.8
 9d26d3a PCI: Put PCIe ports into D3 during suspend
  In 4.11
 8d2c453 platform/x86: dell-laptop: Add Latitude 7480 and others to the DMI 
whitelist

  We need these 2 commits to have better s2idle support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1693393/+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 1609606] Re: Mic mute hotkey does not work on usb keyboard [03f0:2f4a]

2019-07-29 Thread AceLan Kao 
** Changed in: linux (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/1609606

Title:
  Mic mute hotkey does not work on usb keyboard [03f0:2f4a]

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:
  Press the MIC mute function key on the USB keyboard [03f0:2f4a]
  doesn't emit any keyevent nor acpi event.

  T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 23 Spd=1.5 MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=03f0 ProdID=2f4a Rev=00.10
  S:  Manufacturer=Chicony
  S:  Product=HP Business Slim Keyboard
  C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1609606/+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 1616318] Re: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times

2019-07-29 Thread AceLan Kao 
** Changed in: linux (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/1616318

Title:
   System hang when plug/pull USB 3.1 key via thunderbolt port over 5
  times

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:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter to Dekstop.
  3) Insert the USB 3.1 key in the thunderbolt port.
  4) Remove the USB 3.1 key from the thunderbolt port.
  5) Insert the USB 3.1 key in the thunderbolt port.

  Expected results: Can detect the USB 3.1 key and system will not hang.

  Actual results: System Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1616318/+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 1630857] Re: Dell Precision Trackpoint not working after suspend

2019-07-29 Thread AceLan Kao 
** Changed in: linux (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/1630857

Title:
   Dell Precision Trackpoint not working after suspend

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:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter Desktop.
  3) Suspend system.
  4) Using the trackpoint.
  5) Click the left button with DualPoint stick.
  6) Click the right button with DualPoint stick.
  7) Click the middle button with DualPoint stick.
  8) Double-click the left button with DualPoint stick.

  Expected results: Trackpoint and DualPoint stick can work after
  suspend.

  Actual results: Trackpoing and DualPoint stick not working after
  suspend.

  Manufacturer: Dell Inc.

  ProductName: Precision 7500

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1630857/+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 1634380] Re: BT still shows off after resume by wireless hotkey

2019-07-29 Thread AceLan Kao 
** Changed in: linux (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/1634380

Title:
  BT still shows off after resume by wireless hotkey

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:
  Summary: BT still shows off after resume by wireless hotkey

  Steps:
  1) Install ubuntu 16.04
  2) Press the wireless hotkey
  3) Check the WiFi/BT status
  4) Press the wireless hotkey again
  5) Check the WiFi/BT status

  Expected results: Can turn on/off the WiFi/BT by wireless hotkey

  Actual results:
  Can turn off the WiFi/BT by wireless hotkey, but the BT is still off after 
press the hotkey again.
  WiFi didn't has this issue.
  Can't turn on the BT in the system setting, need reboot the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1634380/+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 1695216] Re: Can't disable USB port from BIOS

2019-07-29 Thread AceLan Kao 
** Changed in: linux (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/1695216

Title:
  Can't disable USB port from BIOS

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:
  From BIOS, there is front USB port disable function. It is supposed the 
option in BIOS can
  disable USB port and due to AMD chip limitation, it need OS’s cowork.
  Otherwise the USB disable function will be invalid when resuming from S3 or 
reinsert USB device.

  === SRU Justification ===

  [Impact]
  In BIOS, there is front USB port disable function.
  It is supposed the option in BIOS can disable USB port, but due to AMD chip's
  limitation, it needs OS’s cowork. Otherwise the USB disable function will
  be invalid when resuming from S3 or reinsert USB device.

  [Fix]
  After checking with Windows, we found there are 2 bits that are default on
  in Ubuntu is disabled in Windows. They are
  #define PORT_WKOC_E (1<<22) /* wake on overcurrent 
(enable) */
  #define PORT_WKCONN_E   (1<<20) /* wake on connect (enable) */
  So, this patch introduce a quirk to not setup the wakeup bits only for
  AMD USB chips.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  This patch only affects the listed USB ID, and we don't cert this kind of
  wakeup method, so should have no regression concerns.
  Wake up from USB device is still working, and the patch behavior is confirmed 
by
  the project lead, Tsai, Nicholas, from AMD in the discussion thread[1].

  [Misc]
  This patch is accepted by the maintainer but still not shown up in any git 
tree
  yet. The discussion thread can be found here[1]. To fit the project schedule,
  we need this commit in our kernel as soon as possbile, and can't wait to
  next SRU release cycle.

  1. https://www.spinics.net/lists/linux-usb/msg157789.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1695216/+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 1825958] Re: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740

2019-04-26 Thread AceLan Kao 
** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-oem (Ubuntu Bionic)
   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/1825958

Title:
  Screen freeze after resume from S3 when HDMI monitor plugged on Dell
  Precision 7740

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  [Summary]
  Screen freeze after resume from S3 when HDMI monitor plugged.
  This bug can be reproduced in both AC/DC mode.
  This bug can be reproduced after disabled TLP.

  In kernel log,
  [ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13
  [ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x08008001
  [ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at 
page 81919507, read from 'TC2' (0x54433200) (8)
  [ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.919333] amdgpu

[Group.of.nepali.translators] [Bug 1796634] Re: [0cf3:e007] Can't turn on BT by Wireless hotkey

2018-11-21 Thread AceLan Kao 
** Changed in: linux-firmware (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/1796634

Title:
  [0cf3:e007] Can't turn on BT by Wireless hotkey

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in Gaming Edition:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The issue has been found on new Dell laptop with DW1820 combo card(BT is 
[0cf3:e007])
  1) Use wireless hotkey to turn off WiFi/BT.
  2) Wait 5 minutes.
  3) Use wireless hotkey to turn on WiFi/BT.
  4) Wifi is back, but BT is still off
  5) Only reboot can recovery the BT state

  [Fix]
  Qualcomm releases a new firmware to fix it.

  [Regression Potential]
  Can't evaluate it, but from our verification and S3 stress test,
  there is no any issues result from the firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1796634/+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 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z

2018-07-05 Thread AceLan Kao 
** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1774306

Title:
  enable mic-mute hotkey and led on Lenovo M820z and M920z

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

Bug description:
  [Impact]
  M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button 
with
  led on them, without this patch, the hotkey and led only works on M810z, if we
  want 820z and 920z to work, we need to add their subsystem id in the driver, 
but
  since they use same codec with same pin conf, we use a better way than adding 
id.

  [Fix]
  With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY.

  [Test Case]
  press mic-mute button, then check sound-setting, we found the input will mute 
or
  unmute as users press button, and led will on or off to indicate the input 
status.

  [Regression Potential]
  Very low, through the strictly match the pin conf, codec id and vendor id, 
this
  fix only apply to M810z, M820z and M920z.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1774306/+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 1734242] Re: Intel 9260/9462/9560 driver support

2018-07-01 Thread AceLan Kao 
** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

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

Title:
  Intel 9260/9462/9560 driver support

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  Some new 9260/9462/9560 module doesn't work on artful kernel(v4.13) and 
require some commits
  They are
  https://marc.info/?l=linux-wireless=151076478931107=2
  https://marc.info/?l=linux-wireless=151082205418762=2
  https://marc.info/?l=linux-wireless=151082213518769=2

  Those commits have not been merged into iwlwifi-next yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734242/+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 1748853] Re: Intel 9462 A370:42A4 doesn't work

2018-06-11 Thread AceLan Kao 
** No longer affects: linux

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

Title:
  Intel 9462 A370:42A4 doesn't work

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

Bug description:
  [Impact]
  The PCI ID [A370:42A4] is not included in iwlwifi driver, so that Intel 9462 
with that ID won't work.

  [Fix]
  According the 2 patches sent to 4.15 stable, which were not be included 
before 4.15 EOL, so we cherry pick the 2 patches to Ubuntu 4.15 kernel.
  https://www.spinics.net/lists/stable/msg235420.html

  [Regression Potential]
  Adding IDs, no regression could be happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1748853/+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 1763271] Re: [8086:3e92] display becomes blank after S3

2018-04-24 Thread AceLan Kao 
** Changed in: linux-oem (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/1763271

Title:
  [8086:3e92] display becomes blank after S3

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

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  dmesg:
  [ 60.546305] [drm:intel_dp_start_link_train [i915]] Link Training failed at 
link rate = 54, lane count = 4

  Xorg.0.log:
  [ 60.748] (EE) modeset(0): failed to set mode: Invalid argument
  [ 60.748] (WW) modeset(0): hotplug event: connector 48's link-state is BAD, 
tried resetting the current mode. You may be left with a black screen if this 
fails...

  [Fix]
  Looks like link training fallback fails sometimes with eDP, we need this 
commit to fix the issue.

  commit a306343bcd7df89d9d45a601929e26866e7b7a81 (refs/bisect/bad)
  Author: Manasi Navare 
  Date: Thu Oct 12 12:13:38 2017 -0700

  drm/i915/edp: Do not do link training fallback or prune modes on
  EDP

  [Regression Potential]
  Should be low.
  To avoid conflicts, we introduce 4 commits, I'll try explaining them below

  a306343 drm/i915/edp: Do not do link training fallback or prune modes on EDP
     This is the fix commit and the behavior only changes when DP is eDP, it 
does nothing if DP is eDP. Should be fine to not do link training fallback and 
not emit Hotplug Uevent to userspace to start modeset, since its eDP, the 
display is fixed.

  1853a9d drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp
  7b91bf7 drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp
     Above 2 commits do function name renaming only.

  dc911f5 drm/i915/edp: Allow alternate fixed mode for eDP if available.
     Change the prototype of function "intel_panel_init()" and adding one extra 
argument, should have small impact on the display.

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

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

[Group.of.nepali.translators] [Bug 1748345] Re: QCA9377 requires more IRAM banks for its new firmware

2018-03-19 Thread AceLan Kao 
** No longer affects: linux-firmware (Ubuntu)

** No longer affects: linux-firmware (Ubuntu 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/1748345

Title:
  QCA9377 requires more IRAM banks for its new firmware

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

Bug description:
  [Impact]
  The new firmware for QCA9377 supports Qualcomm's RED(Radio Equipment 
Directive) compliance and requires more IRAM banks. The origin 4 banks doesn't 
fit the new BDF and firmware.

  [Fix]
  Change the bank number from 4 to 9.

  [Regression Potential]
  Low, increasing the number of IRAM banks should be no harm.

  [Misc]
  Currently, both driver patch and new firmware do not upstream yet. For the 
sake of avoiding dkms package, we can change t
  he IRAM bank number before their patch is ready.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1748345/+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 1748345] Re: QCA9377 requires more IRAM banks for its new firmware

2018-03-19 Thread AceLan Kao 
** Also affects: linux-firmware (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  QCA9377 requires more IRAM banks for its new firmware

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

Bug description:
  [Impact]
  The new firmware for QCA9377 supports Qualcomm's RED(Radio Equipment 
Directive) compliance and requires more IRAM banks. The origin 4 banks doesn't 
fit the new BDF and firmware.

  [Fix]
  Change the bank number from 4 to 9.

  [Regression Potential]
  Low, increasing the number of IRAM banks should be no harm.

  [Misc]
  Currently, both driver patch and new firmware do not upstream yet. For the 
sake of avoiding dkms package, we can change t
  he IRAM bank number before their patch is ready.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1748345/+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 1751805] Re: linux-oem: -proposed tracker

2018-03-07 Thread AceLan Kao 
** Changed in: kernel-sru-workflow/prepare-package-lbm
   Status: Invalid => In Progress

** Changed in: kernel-sru-workflow/prepare-package-ports-meta
   Status: Invalid => In Progress

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

Title:
  linux-oem: 4.13.0-1022.24 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lbm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-ports-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1751798
  phase: Packaging

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

2018-03-07 Thread AceLan Kao 
** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.13.0-1022.24 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-ports-meta
   Status: Invalid => In Progress

** Changed in: kernel-sru-workflow/prepare-package-ports-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Status: Invalid => In Progress

** Changed in: kernel-sru-workflow/prepare-package-lbm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

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

Title:
  linux-oem: 4.13.0-1022.24 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lbm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-ports-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1751798
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1751805/+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 1734243] Re: Intel 9260/9462/9560 firmware support

2018-02-04 Thread AceLan Kao 
** Changed in: linux-firmware (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

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

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Zesty:
  Won't Fix
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1734243/+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 1734242] Re: Intel 9260/9462/9560 driver support

2018-01-15 Thread AceLan Kao 
** Changed in: linux (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/1734242

Title:
  Intel 9260/9462/9560 driver support

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

Bug description:
  Some new 9260/9462/9560 module doesn't work on artful kernel(v4.13) and 
require some commits
  They are
  https://marc.info/?l=linux-wireless=151076478931107=2
  https://marc.info/?l=linux-wireless=151082205418762=2
  https://marc.info/?l=linux-wireless=151082213518769=2

  Those commits have not been merged into iwlwifi-next yet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734242/+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 1736639] Re: Intel 9260/9462/9560 can't connect to 5GHz AP

2018-01-15 Thread AceLan Kao 
** Changed in: linux (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/1736639

Title:
  Intel 9260/9462/9560 can't connect to 5GHz AP

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

Bug description:
  With 1009 oem(v4.13) kernel and latest linux-firmware[1], it connect to 
2.4GHz APs without any issues.
  But it fails to connect 5GHz APs.

  It stucks when I select a 5GHz network AP, and after timeout it
  connects to another configured 2.4GHz AP.
  [ 512.404139] wlp0s20f3: authenticate with 2c:36:f8:fa:ec:00
  [ 512.410781] wlp0s20f3: send auth to 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.449561] wlp0s20f3: authenticated
  [ 512.450625] wlp0s20f3: associate with 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.452010] wlp0s20f3: RX AssocResp from 2c:36:f8:fa:ec:00
  (capab=0x111 status=0 aid=8)
  [ 512.454501] wlp0s20f3: associated
  [ 512.542439] wlp0s20f3: Limiting TX power to 27 (30 - 3) dBm as
  advertised by 2c:36:f8:fa:ec:00
  [ 557.685247] wlp0s20f3: deauthenticating from 2c:36:f8:fa:ec:00 by
  local choice (Reason: 3=DEAUTH_LEAVING)
  [ 557.695875] wlp0s20f3: failed to remove key (1, ff:ff:ff:ff:ff:ff)
  from hardware (-22)

  1. c4276b6 (tag: refs/tags/iwlwifi-fw-2017-11-03) iwlwifi: add
  firmware version 33 for new 9000 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736639/+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 1730544] Re: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

2018-01-10 Thread AceLan Kao 
** Changed in: linux (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/1730544

Title:
  AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

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

Bug description:
  From vendor's suggestion, there are some patches in v4.14-rc6 are
  required to enable the 2 NICs

  417a3ae net: aquantia: Bad udp rate on default interrupt coalescing
  b82ee71 net: aquantia: Enable coalescing management via ethtool interface
  6849540 net: aquantia: mmio unmap was not performed on driver removal
  4c8bb60 net: aquantia: Limit number of MSIX irqs to the number of cpus
  93d87b8 net: aquantia: Fixed transient link up/down/up notification
  5d8d84e net: aquantia: Add queue restarts stats counter
  65e665e net: aquantia: Reset nic statistics on interface up/down

  And to avoid conflict, cherry pick 2 more commits

  3aec641 aquantia: Fix Tx queue hangups
  65e665e net: aquantia: Reset nic statistics on interface up/down

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1730544/+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 1706833] Re: atheros bt failed after S3

2017-10-04 Thread AceLan Kao 
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: hwe-next
   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/1706833

Title:
  atheros bt failed after S3

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:
  [Impact]
  BT fails to load firmware after S3. On my system it's atheros' chip, but the 
same issue can be seen with broadcom's chip, too.
 [542.6274] WARNING: CPU: 0 PID: 20729 at 
/build/linux-MD8jsN/linux-4.4.0/drivers/base/firmware_class.c:1148 
_request_firmware+0x7c2/0xaf0()

  The root cause of this issue is request_firmware() is being called at
  the wrong time.

  [Fix]
  The fix is from this old thread[1], but the patch didn't be accepted by the 
maintainer.
  It prevents the work queue from being re-created and calls request_firmware() 
immediately before usermodehelper is fully resumed. Making the workqueue 
freezable preserves the delay and will postpone the firmware loading time.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  From what I can see, I think this change should be safe, and after 240 times 
S3 test, the system and BT functions are still working.

  1. http://lists.openwall.net/netdev/2015/05/06/3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1706833/+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 1705633] Re: [8087:0a2b] Failed to load bluetooth firmware(might affect some other Intel bt devices)

2017-09-19 Thread AceLan Kao 
** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  [8087:0a2b] Failed to load bluetooth firmware(might affect some other
  Intel bt devices)

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:
  [Impact]
  After this linux-firmware bug[1] update the firmware files, it removes 
intel/ibt-11-16.{ddc,sfi} and add intel/ibt-12-16.{ddc,sfi}, but in btusb 
driver, it hardcoded the hw_variant as 11. So we got this kind of error after 
the linux-firmware package updated and lost the bt functions.

  [5.516003] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.516181] bluetooth hci0: Direct firmware load for intel/ibt-11-16.sfi 
failed with error -2
  [5.516183] Bluetooth: hci0: Failed to load Intel firmware file (-2)

  [Fix]
  This patch uses a hw_variant variable to replace the hardcoded 11.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  The hw_variant variable has shown up since kernel 3.10 in this commit
 dffd30e Bluetooth: Add support for Intel Bluetooth device [8087:07dc]
  So, we don't have to worry about old chips don't contains this info, since it 
exists
  and be used for a very long time.

  1. https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1686815

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1705633/+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 1662763] Re: Intel I210 ethernet does not work both after S3

2017-03-02 Thread AceLan Kao 
** 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/1662763

Title:
   Intel I210 ethernet does not work both after S3

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

Bug description:
  Steps:
  1. Only plug ethernet cable to Intel I210 Gigabit Ethernet
  2. Check Intel I210 Gigabit Ethernet can be worked
  3. Enter into S3
  4. Resume from S3
  5. Check Intel I210 Gigabit Ethernet Ethernet

  Expected results: Intel I210 Gigabit Ethernet works normally

  Actual results: Intel I210 Gigabit Ethernet does not work after S3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1662763/+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 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

2017-01-24 Thread AceLan Kao 
** Changed in: hwe-next/vivid
   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/1625932

Title:
  Backlight does not change when adjust it higher than 50% after S3

Status in HWE Next:
  Fix Released
Status in HWE Next vivid series:
  Won't Fix
Status in HWE Next xenial series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1625932/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%

2017-01-24 Thread AceLan Kao 
** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Won't Fix

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

Title:
  Backlight sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Won't Fix
Status in xorg source package in Vivid:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in xorg source package in Xenial:
  Invalid

Bug description:
  Back-light sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

  Issue is interment in occurrence. Will be reproducible with the
  command "sudo pm-suspend" & or close/reopen laptop lid for a period of
  time days or hours, then go a period of time, days or hours without
  being able to trigger it again.

  This is irrespective of running "apt-get update && apt-get upgrade -y"
  and has continued to be intermittent on last 3 versions of 3.19
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-74-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec  1 10:06:43 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06e5]
  InstallationDate: Installed on 2016-11-22 (8 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed 
root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.14
  dmi.board.name: 0W7V82
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec  1 09:14:43 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1648279] Re: Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

2017-01-10 Thread AceLan Kao 
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: hwe-next
   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/1648279

Title:
  Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

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

Bug description:
  [Steps]
  1. install trusty image
  2. "sudo apt-get update" and install available updates to enable upgrading in 
images
  3. enable Trusty -proposed ppa
  4. "sudo apt-get update"
  5. "sudo apt-get dist-upgrade && sudo apt-get install --install-recommends 
linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial"
  6. Reboot system
  7. Check Ethernet

  [Expected results]
  Ethernet work

  [Actual results]
  Ethernet not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1648279/+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 1641562] Re: [SRU] Add 0cf3:e009 to btusb

2016-12-19 Thread AceLan Kao 
Bt 4.0 keyboard can be paired with kernel 4.4.0-57

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

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

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

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

Title:
  [SRU] Add 0cf3:e009 to btusb

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

Bug description:
  Otherwise can't pair this bluetooth device with BLE devices, need to
  backport to Xenial and Yakkety.

  commit 935199348048902124d0b288788c3a45e78b69ab
  Author: Kai-Heng Feng 
  Date:   Tue Aug 16 12:50:06 2016 +0800

  Bluetooth: btusb: Add support for 0cf3:e009
  
  Device 0cf3:e009 is one of the QCA ROME family.
  
  T:  Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#=  4 Spd=12  MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0cf3 ProdID=e009 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  
  Signed-off-by: Kai-Heng Feng 
  Signed-off-by: Marcel Holtmann 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1641562/+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 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open

2016-11-08 Thread AceLan Kao 
The patch has CC'ed stable, so it won't affect the release with kernel
newer than 4.6

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

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

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

Title:
  [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid
  close/open

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

Bug description:
  Touchscreen fails to function after resume from s3 by Lid close/open

  Suspend from power menu/ power button cannot reproduce this issue

  Steps:
  1. Install ubuntu 16.04 and boot to OS
  2. suspend the system by Lid close action
  3. resume the session by Lid open
  4. check if touchscreen function works

  Expected results: Touchscreen should still works after Lid open

  Actual results: Touchscreen fails to work after lid open

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1632527/+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 1616781] Re: DINO2M - System hangs with a black screen during s4 stress test

2016-09-25 Thread AceLan Kao 
** Changed in: linux (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/1616781

Title:
  DINO2M - System hangs with a black screen during s4 stress test

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

Bug description:
  System hangs with a black screen during s4 stress test

  Keyboard backlight LED is still on and adjustable, but tty1 is not avalible 
to switch to.
  System needs to be hardware shutdown.

  Steps:
  1. install Ubuntu 16.04 and boot to OS
  2. run s4 stress test (30 cycles)
  3. check if the test can be completed

  Expected results: Test should be able to be completed

  Actual results: System hangs with a black screen

  Additional information:
  BIOS: 99.2.22

  CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4x)

  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 5916
  (rev 02)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1616781/+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 1609204] Re: Power Menu does not display after press the Power Button

2016-08-29 Thread AceLan Kao 
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: hwe-next
   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/1609204

Title:
   Power Menu does not display after press the Power Button

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:
  Steps:
  1) Install BTO and boot into OS
  2) Press the Power Button

  Expected results: Power Menu should display after press the Power
  Button

  Actual results: Power Menu does not display after press the Power
  Button

  Manufacturer: Dell Inc.
  ProductName: XPS 13
  BiosVersion: 0.1.4

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