[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-04-20 Thread Andy Chi
I can reproduce this issue on hirsute.
Information below is the mesa version.

libegl-mesa0:amd64  21.0.1-2
libgbm1:amd64   21.0.1-2
libgl1-mesa-dri:amd64   21.0.1-2
libglapi-mesa:amd64 21.0.1-2
libglx-mesa0:amd64  21.0.1-2
libxatracker2:amd64 21.0.1-2
mesa-vulkan-drivers:amd64   21.0.1-2


** Attachment added: "sosreport-u-Inspiron-3891-2021-04-21-jcddohr.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490468/+files/sosreport-u-Inspiron-3891-2021-04-21-jcddohr.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-04-21 Thread Andy Chi
Version of mesa on oibaf ppa
21.2~git2104200600.4a384f~oibaf~h
(note)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-04-22 Thread Andy Chi
Reproduce with kernel cod/tip/drm-tip/2021-04-22 Mainline on hirsute.

** Attachment added: "sosreport-u-Inspiron-3891-2021-04-22-rurdrvj.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490976/+files/sosreport-u-Inspiron-3891-2021-04-22-rurdrvj.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-04-22 Thread Andy Chi
Test pass with newer mesa version from oibaf ppa.

libegl-mesa0:amd64 21.2~git2104200600.4a384f~oibaf~h
libgbm1:amd64 21.2~git2104200600.4a384f~oibaf~h
libgl1-mesa-dri:amd64 21.2~git2104200600.4a384f~oibaf~h
libglapi-mesa:amd64 21.2~git2104200600.4a384f~oibaf~h
libglx-mesa0:amd64 21.2~git2104200600.4a384f~oibaf~h
libxatracker2:amd64 21.2~git2104200600.4a384f~oibaf~h
mesa-vulkan-drivers:amd64 21.2~git2104200600.4a384f~oibaf~h

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] [NEW] Add Dell Privacy Mic Mute Key

2021-04-28 Thread Andy Chi
Public bug reported:

[Impact]

 * New Dell machine will support new Dell privacy function,
   such as Mic Mute. If the hwdb file does not update, userspace won't
   get notification.

[Test Plan]

 * Use a Dell machine, which has Dell privacy function, and press mic mute key.
   GUI will pop up "Mic Mute" icon.


[Where problems could occur]

 * This change adds new hwdb, will not impact other hardware.


[Other Info]
 
 * This change has been verified on Dell machine.

** Affects: oem-priority
 Importance: Undecided
 Assignee: Andy Chi (andch)
 Status: New

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1895961 somerville

** Tags added: oem-priority originate-from-1895961 somerville

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * New Dell machine will support new Dell privacy function,
 such as Mic Mute. If the hwdb file does not update, userspace won't
 get notification.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  
  [Where problems could occur]

   * This change adds new hwdb, will not impact other hardware.

  
  [Other Info]
   
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-04-28 Thread Andy Chi
Upload debdiff of focal.

** Patch added: "systemd_245.4-4ubuntu3.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926547/+attachment/5493226/+files/systemd_245.4-4ubuntu3.7.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-04-29 Thread Andy Chi
Upload debdiff of hirsute.

** Patch added: "systemd_247.3-3ubuntu3.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926547/+attachment/5493239/+files/systemd_247.3-3ubuntu3.1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-05-23 Thread Andy Chi
Hello @ddstreet,
Is Groovy also need to apply this change? I thought it's non LTS, so I didn't 
make diff file.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-05-26 Thread Andy Chi
Hi @Dan,
Audio doesn't work on the platform since lack of SRU LP#1924970, I locally 
build a workable alsa-ucm-conf and systemd to test mic mute key on groovy for 
the platform. Also it needs oem kernel to support Dell Privacy. Since audio is 
not supported on groovy, could we pass it? Can we proceed for focal first?

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-05-28 Thread Andy Chi
Hi @Dan,
No, the patch won't break anything in groovy.

Thanks for help.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-06-02 Thread Andy Chi
Test with machine which supports Dell privacy. Mic mute key works well
in groovy and focal.

[kernel version]
linux-oem-20.04b (1029)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-10-22 Thread Andy Chi
** Changed in: oem-priority/focal
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project focal series:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] [NEW] Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-11-30 Thread Andy Chi
Public bug reported:

[Impact]

 * Dell introduces new function called Dell Privacy, it utilizes
hardware mute to control audio and camera. The commit map the reported
key event to mic mute for making userspace can work as before, "Mic
Mute" dialog pop-up while the mic mute button is pressed.

[Test Plan]

 * Use a Dell machine, which has Dell privacy function, and press mic mute key.
   GUI will pop up "Mic Mute" icon.

[Where problems could occur]

 * This change adds key event mapping in hwdb, which won't impact other
hardware.

 any regression would likely cause problems with key(s) from the
specific dell kb matching the modified listing in the hw db.

[Other Info]

 * This change has been verified on Dell machine.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952735] [NEW] Add Microphone mute key mapping for Dell machine

2021-11-30 Thread Andy Chi
Public bug reported:

[Impact]

 * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
[Test Plan]

 * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
   GUI will pop up "Mic Mute" icon.

[Where problems could occur]

 * This change adds key event mapping in hwdb, which won't impact other
hardware.

 any regression would likely cause problems with key(s) from the
specific dell kb matching the modified listing in the hw db.

[Other Info]

 * This change has been verified on Dell machine.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952735

Title:
  Add Microphone mute key mapping for Dell machine

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine

2021-11-30 Thread Andy Chi
Upload debdiff for focal

** Patch added: "systemd_245.4-4ubuntu3.14.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952735/+attachment/5544344/+files/systemd_245.4-4ubuntu3.14.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952735

Title:
  Add Microphone mute key mapping for Dell machine

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-11-30 Thread Andy Chi
Upload debdiff for focal

** Patch added: "systemd_245.4-4ubuntu3.14.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952733/+attachment/5544343/+files/systemd_245.4-4ubuntu3.14.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-11-30 Thread Andy Chi
Upload debdiff for hirsute

** Patch added: "systemd_247.3-3ubuntu3.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952733/+attachment/5544369/+files/systemd_247.3-3ubuntu3.7.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-11-30 Thread Andy Chi
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-11-30 Thread Andy Chi
update debdiff for impish

** Patch added: "systemd_248.3-1ubuntu9.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952733/+attachment/5544371/+files/systemd_248.3-1ubuntu9.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine

2021-11-30 Thread Andy Chi
Upload debdiff for hirsute

** Patch added: "systemd_247.3-3ubuntu3.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952735/+attachment/5544368/+files/systemd_247.3-3ubuntu3.7.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952735

Title:
  Add Microphone mute key mapping for Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine

2021-11-30 Thread Andy Chi
Update debdiff for impish

** Patch added: "systemd_248.3-1ubuntu9.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952735/+attachment/5544370/+files/systemd_248.3-1ubuntu9.debdiff

** Tags added: oem-priority originate-from-1950435 somerville

** Tags added: originate-from-1950547

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Tags removed: originate-from-1950435

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952735

Title:
  Add Microphone mute key mapping for Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-11-30 Thread Andy Chi
** Tags added: oem-priority originate-from-1950435 somerville

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine

2021-12-13 Thread Andy Chi
Test on Dell machine, mic mute key works well in focal.

[kernel version]
linux-oem-20.04d (1011)

[systemd version]
245.4-4ubuntu3.14

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952735

Title:
  Add Microphone mute key mapping for Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-12-13 Thread Andy Chi
Test with machine which supports Dell privacy. Mic mute key works well
in focal.

[kernel version]
linux-oem-20.04d (1011)

[systemd version]
245.4-4ubuntu3.14

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine

2021-12-13 Thread Andy Chi
Test on Dell machine, mic mute key works well in impish.

[kernel version]
linux-oem-20.04d (1011)

[systemd version]
248.3-1ubuntu8.1


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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952735

Title:
  Add Microphone mute key mapping for Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-12-13 Thread Andy Chi
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-12-13 Thread Andy Chi
Test with machine which supports Dell privacy. Mic mute key works well
in impish.

[kernel version]
linux-oem-20.04d (1011)

[systemd version]
248.3-1ubuntu8.1

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-12-16 Thread Andy Chi
It should also use oem kernel which mentioned in comment #15

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1926547

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project focal series:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-06-17 Thread Andy Chi
** Tags added: originate-from-1931964

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-22 Thread Andy Chi
update debdiff of groovy.

** Patch added: "bluez_5.55-0ubuntu1.3~1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933221/+attachment/5506235/+files/bluez_5.55-0ubuntu1.3~1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] [NEW] Blutooth on/off does not work properly from gnome-control-center

2021-06-22 Thread Andy Chi
Public bug reported:

[Impact]

 * On/off of Bluetooth in gnome-control-center will not work properly.

 * Devices are not refreshed in the list anymore.

 * The passed struct will depend on the length of the submitted read() and the
   kernel version.

[Test Plan]

 * Open gnome-control-center and select Bluetooth
   
 * turn off Bluetooth via UI
   
 * turn on Bluetooth via UI

[Where problems could occur]

 * If user install newer kernel such as 5.13, they may have this issue.

 * Tested on Intel AX201 and Intel 6235 with kernel version
5.13.0-1003-oem.

 * Upstream bug in gnome-bluetooth
   https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

 * Discussion in linux-bluetooth
   https://marc.info/?t=16200475893&r=1&w=2

** Affects: oem-priority
 Importance: Critical
 Assignee: Andy Chi (andch)
 Status: New

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1931048 somerville

** Attachment added: "debdiff of focal"
   
https://bugs.launchpad.net/bugs/1933221/+attachment/5506234/+files/bluez_5.53-0ubuntu3.3~1.debdiff

** Tags added: oem-priority originate-from-1931048 somerville

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-22 Thread Andy Chi
upload debdiff of hirsute

** Patch added: "bluez_5.56-0ubuntu4.2~1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933221/+attachment/5506236/+files/bluez_5.56-0ubuntu4.2~1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-22 Thread Andy Chi
*** This bug is a duplicate of bug 1926062 ***
https://bugs.launchpad.net/bugs/1926062

Hi @Daniel,
Sorry for that, I tried to search for existing bug, I guess I'm not using the 
right words to search. Will be careful next time or ask in mattermost channel 
first. Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-06-22 Thread Andy Chi
Hi @Daniel,
Yes, it has not been upstreamed yet. Linux-bluetooth does not reply the thread, 
maybe I'll have a try to send mail to them.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in bluez package in Ubuntu:
  In Progress
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth

   * turn off Bluetooth via UI

   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-22 Thread Andy Chi
*** This bug is a duplicate of bug 1926062 ***
https://bugs.launchpad.net/bugs/1926062

Got it, thanks for sharing.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-06-22 Thread Andy Chi
** Changed in: oem-priority
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-06-23 Thread Andy Chi
Hi @Daniel,
I created a public bug in github/bluez, mp is sent by maintainer.
https://github.com/bluez/bluez/issues/162

** Bug watch added: github.com/bluez/bluez/issues #162
   https://github.com/bluez/bluez/issues/162

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-06-23 Thread Andy Chi
Bluez bug (https://github.com/bluez/bluez/issues/162) closed and fix merged in 
bluez.
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=c939747f543a76ffd556312f753cf9d36c047c94

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Unknown
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-06-23 Thread Andy Chi
** Tags added: oem-priority originate-from-1931048 somerville

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Unknown
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-24 Thread Andy Chi
[OS version]
Focal

[kernel version]
5.13-oem

[Step]
1. open gnome-settings
2. turn off Bluetooth by toggle
3. turn on Bluetooth by toggle

It works fine.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-24 Thread Andy Chi
[OS version]
Hirsute

[kernel version]
5.11.0-16-generic

[Step]
1. open gnome-settings
2. turn off Bluetooth by toggle
3. turn on Bluetooth by toggle

It works fine.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

   * Upstream bug in gnome-bluetooth
 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

   * Discussion in linux-bluetooth
 https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-06-29 Thread Andy Chi
** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  New
Status in systemd source package in Groovy:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-06-30 Thread Andy Chi
** Changed in: systemd (Ubuntu Focal)
 Assignee: Kai-Heng Feng (kaihengfeng) => Andy Chi (andch)

** Changed in: systemd (Ubuntu Groovy)
 Assignee: Kai-Heng Feng (kaihengfeng) => Andy Chi (andch)

** Changed in: systemd (Ubuntu Hirsute)
 Assignee: Kai-Heng Feng (kaihengfeng) => Andy Chi (andch)

** Changed in: systemd (Ubuntu Impish)
 Assignee: Kai-Heng Feng (kaihengfeng) => Andy Chi (andch)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-06-30 Thread Andy Chi
Upload debdiff of groovy

** Patch added: "systemd_246.6-1ubuntu1.5~1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930910/+attachment/5508144/+files/systemd_246.6-1ubuntu1.5~1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-06-30 Thread Andy Chi
Upload debdiff of focal

** Patch added: "systemd_245.4-4ubuntu3.8~1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930910/+attachment/5508143/+files/systemd_245.4-4ubuntu3.8~1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-06-30 Thread Andy Chi
Upload debdiff of hirsute

** Patch added: "systemd_247.3-3ubuntu3.2~1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930910/+attachment/5508145/+files/systemd_247.3-3ubuntu3.2~1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-07-05 Thread Andy Chi
Hi @ddstreet,
Thanks. May I know when will systemd in -proposed?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-07-06 Thread Andy Chi
Hi @ddstreet,
May I know when will you create a new systemd release for all the series?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-07-06 Thread Andy Chi
Hi @mic159,
Can you also help to append sos report, BIOS version, `rfkill list` and `lspci 
-nnvv` in the new bug?
Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in
  kernels 5.11 (approximately) onward. Devices are not refreshed in the
  list anymore.

  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-07-09 Thread Andy Chi
[machine]
HP ProBook

[OS]
Hirsute

[systemd version]
247.3-3ubuntu3.2

[test result]
mic mute key works fine.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-07-09 Thread Andy Chi
[machine]
HP ProBook

[OS]
Groovy

[systemd version]
246.6-1ubuntu1.5

[test result]
mic mute key works fine.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2021-07-09 Thread Andy Chi
[machine]
HP ProBook

[OS]
Focal

[systemd version]
245.4-4ubuntu3.8

[test result]
mic mute key works fine.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly

2021-07-12 Thread Andy Chi
[Machine]
HP Elite Gragonfly

[OS]
Focal

[systemd version]
245.4-4ubuntu3.8

[Result]
mic mute key works

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1932352

Title:
  Fix micmute hotkeys on HP Elite Dragonfly

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Mic mute key is no function on HP Elite Dragonfly.

  [Fix]
  After confirming with HP, there are two model names for Dragonfly:
  * HP Elite Dragonfly G2 Notebook PC
  * HP Elite Dragonfly Max Notebook PC
  Thus, the commit 
  Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic 
mute key.

  [Test]
  After patching it, the mic mute key could functioned well on my Dragonfly 
laptop.

  [Where problems could occur]
  There is not old rule for Dragonfly dmi string in current hwdb.
  Which means the Dragonfly is using default HP key map:
  ```
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:*

   KEYBOARD_KEY_81=fn_esc
  ```
  This patch will change the HP machine (if product name contains 
pnHPEliteDragonfly*) to map 81 to mic mute key.
  If a machine (pnHPEliteDragonfly*) works good in the past then this patch may 
cause it's mic mute key become malfunction.
  However, this rule is confirmed/provided from HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly

2021-07-12 Thread Andy Chi
[Machine]
HP Elite Gragonfly

[OS]
Hirsute

[systemd version]
247.3-3ubuntu3.2

[Result]
mic mute key works

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1932352

Title:
  Fix micmute hotkeys on HP Elite Dragonfly

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Mic mute key is no function on HP Elite Dragonfly.

  [Fix]
  After confirming with HP, there are two model names for Dragonfly:
  * HP Elite Dragonfly G2 Notebook PC
  * HP Elite Dragonfly Max Notebook PC
  Thus, the commit 
  Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic 
mute key.

  [Test]
  After patching it, the mic mute key could functioned well on my Dragonfly 
laptop.

  [Where problems could occur]
  There is not old rule for Dragonfly dmi string in current hwdb.
  Which means the Dragonfly is using default HP key map:
  ```
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:*

   KEYBOARD_KEY_81=fn_esc
  ```
  This patch will change the HP machine (if product name contains 
pnHPEliteDragonfly*) to map 81 to mic mute key.
  If a machine (pnHPEliteDragonfly*) works good in the past then this patch may 
cause it's mic mute key become malfunction.
  However, this rule is confirmed/provided from HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly

2021-07-12 Thread Andy Chi
[Machine]
HP Elite Gragonfly

[OS]
groovy

[systemd version]
246.6-1ubuntu1.5

[Result]
mic mute key works

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1932352

Title:
  Fix micmute hotkeys on HP Elite Dragonfly

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Mic mute key is no function on HP Elite Dragonfly.

  [Fix]
  After confirming with HP, there are two model names for Dragonfly:
  * HP Elite Dragonfly G2 Notebook PC
  * HP Elite Dragonfly Max Notebook PC
  Thus, the commit 
  Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic 
mute key.

  [Test]
  After patching it, the mic mute key could functioned well on my Dragonfly 
laptop.

  [Where problems could occur]
  There is not old rule for Dragonfly dmi string in current hwdb.
  Which means the Dragonfly is using default HP key map:
  ```
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:*

   KEYBOARD_KEY_81=fn_esc
  ```
  This patch will change the HP machine (if product name contains 
pnHPEliteDragonfly*) to map 81 to mic mute key.
  If a machine (pnHPEliteDragonfly*) works good in the past then this patch may 
cause it's mic mute key become malfunction.
  However, this rule is confirmed/provided from HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-07-14 Thread Andy Chi
** Tags added: originate-from-1936277

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-07-15 Thread Andy Chi
Upload gnome-settings-daemon debdiff of focal.

** Patch added: "gnome-settings-daemon_3.36.1-0ubuntu2~2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+attachment/5511040/+files/gnome-settings-daemon_3.36.1-0ubuntu2~2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-07-15 Thread Andy Chi
Upload gnome-settings-daemon debdiff of hirsute.

** Patch added: "gnome-settings-daemon_3.38.1-3ubuntu4~1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+attachment/5511041/+files/gnome-settings-daemon_3.38.1-3ubuntu4~1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-07-15 Thread Andy Chi
[Impact]

Bluetooth cannot turn on after disabling AirPlane mode

[Test Plan]

1. Open gnome-control-center and select Wi-Fi
2. Turn off Wi-Fi via UI
3. Select Bluetooth column
4. Turn off Bluetooth via UI
5. Turn Off AirPlane Mode in Bluetooth menu

[Where problems could occur]

Since the fix involves the 'rfkill' logic it has the potential to affect
any Bluetooth or Wifi on/off setting.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2021-07-21 Thread Andy Chi
Test on HP desktop with following steps

1. Open gnome-control-center and select Wi-Fi
2. Turn off Wi-Fi via UI
3. Select Bluetooth column
4. Turn off Bluetooth via UI
5. Turn Off AirPlane Mode in Bluetooth menu

Bluetooth works fine.

[OS]
Focal

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  Fix Committed
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-07-26 Thread Andy Chi
I enable -proposed and do a dist-upgrade, made sure 21.0.3-0ubuntu0.2 is
installed, then reboot and run stress-ng:

$ stress-ng --stack 0 --timeout 300
stress-ng: info: [1936] dispatching hogs: 8 stack
stress-ng: info: [1936] successful run completed in 300.88s (5 mins, 0.88 secs)

The desktop session didn't crash so it's still alive.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855

Title:
  Xorg xserver got signal 6 to abort

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-07-30 Thread Andy Chi
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855

Title:
  Xorg xserver got signal 6 to abort

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-10-27 Thread Andy Chi
** Tags added: originate-from-1994098 stella

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  `/var/cache/pbuilder/build/276481/build/grub2-2.

[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-10-31 Thread Andy Chi
Download ubuntu-20.04.5-desktop-amd64.iso and try to install on a HP
laptop, I can't boot into installation menu. If initrd.img lower than
100MB then everything is fine.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx

[Touch-packages] [Bug 1999782] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

2022-12-15 Thread Andy Chi
** Package changed: systemd-hwe (Ubuntu) => systemd (Ubuntu)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1999782

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerator.

  [ Test Plan ]

   * On Dell laptops with model SKU 0C00 or 0C02

   * Rotate the laptop and the display should not be rotated.

  [ Where problems could occur ]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

  [ Other info ]
   * Commit backport from Upstream:
 https://github.com/systemd/systemd/pull/25724

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1999782/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1999782] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

2022-12-16 Thread Andy Chi
** Package changed: systemd (Ubuntu) => systemd-hwe (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1999782

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd-hwe package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerator.

  [ Test Plan ]

   * On Dell laptops with model SKU 0C00 or 0C02

   * Rotate the laptop and the display should not be rotated.

  [ Where problems could occur ]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

  [ Other info ]
   * Commit backport from Upstream:
 https://github.com/systemd/systemd/pull/25724

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1999782/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad

2023-02-07 Thread Andy Chi
** Tags added: originate-from-2001891 somerville

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1977986

Title:
  UPower and battery indicator show update in 2 minutes  when connecting
  power cable ThinkPad

Status in OEM Priority Project:
  In Progress
Status in upower package in Ubuntu:
  New

Bug description:
  We found this issue on several ThinkPad. The upower will change
  'pending-charge' to 'charging' after 2 minutes later, but the
  /sys/class/power_supply/BAT0/status changes to 'Charging' immediately
  when connecting the power cable.

  $ upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Sunwoda
model:5B10W13975
serial:   34226
power supply: yes
updated:  Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  55.94 Wh
  energy-empty:0 Wh
  energy-full: 57 Wh
  energy-full-design:  57 Wh
  energy-rate: 5.79 W
  voltage: 16.688 V
  percentage:  98%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  1654702882  98.000  pending-charge
  1654702863  97.000  pending-charge
History (rate):
  1654702863  5.790   pending-charge
  1654702863  6.171   pending-charge

  $ cat /sys/class/power_supply/BAT0/status 
  Charging

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1977986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-06-16 Thread Andy Chi
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Impish:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2022-06-16 Thread Andy Chi
** Changed in: oem-priority
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome in Wayland

2022-08-12 Thread Andy Chi
I use xps 9310 with 22.04 but I change my windows server back to X.org
and I passed the memory stress test.

** Attachment added: "sosreport-ubuntu-XPS-13-9310-2022-08-11-gjqxynj.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1985887/+attachment/5608038/+files/sosreport-ubuntu-XPS-13-9310-2022-08-11-gjqxynj.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1985887

Title:
  systemd kills gnome-shell or gnome-terminal if gnome in Wayland

Status in systemd package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  0. Install Jammy image
  1. open gnome terminal
  2. issue stress_ng or Canonical certification tool checkbox as
  "checkbox-cli run com.canonical.certification::memory/memory_stress_ng"
  3. Terminal or Gnome-shell will be killed by systemd-oomd

  It's because all stressors are under same cgroup.

  So far, it only happen in Wayland.

  over ssh and in multi-user.target work good.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2051181] [NEW] apt cannot upgrade packages if the current security version is same as updates

2024-01-24 Thread Andy Chi
Public bug reported:

When I finished installation with Jammy 22.04.3, I noticed that nvidia-
driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-
upgrade`.

Below is the log of apt upgrade:
ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run  

  [2/1878]
Reading package lists... Done   

  
Building dependency tree... Done

  
Reading state information... Done
Entering ResolveByKeep 10%
  Dependencies are not satisfied for nvidia-driver-535:amd64 < 
535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib >
Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on 
nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 
535.129.03-1)
  Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends
  Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 
< 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib >
Keeping package linux-modules-nvidia-535-oem-22.04c:amd64
  Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 
< 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib >
Package linux-modules-nvidia-535-oem-22.04c:amd64 
linux-modules-nvidia-535-oem-22.04c:amd64 Depends on 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 
6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27)
  Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends
  Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN 
Ib >
Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64
  Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64
  Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 
@ii umU > (= 6.1.0-1027.27)
  Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends
  Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-objects-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 
6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27)
  Keeping Package linux-objects-nvidia-535-6.1.0-1027-oem:amd64 due to Depends

https://pastebin.canonical.com/p/7frwTKZG6D/

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2051181

Title:
  apt cannot upgrade packages if the current security version is same as
  updates

Status in apt package in Ubuntu:
  New

Bug description:
  When I finished installation with Jammy 22.04.3, I noticed that
  nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt
  dist-upgrade`.

  Below is the log of apt upgrade:
  ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run

[2/1878]
  Reading package lists... Done 


  Building dependency tree... Done  


  Reading state information... Done
  Entering ResolveByKeep 10%
Dependencies are not satisfied for nvidia-driver-535:amd64 < 
535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib >
  Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on 
nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 
535.129.03-1)
Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends
  

[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

2022-03-15 Thread Andy Chi
** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

2022-03-23 Thread Andy Chi
** Tags added: originate-from-1966014

** Tags added: originate-from-1965898

** Tags added: originate-from-1964913

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1955997

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Impish:
  In Progress
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

2022-03-24 Thread Andy Chi
** Tags removed: originate-from-1964913 originate-from-1965898
originate-from-1966014

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1955997

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Impish:
  In Progress
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966179] [NEW] The airplane hotkey does not work on lots of HP platforms

2022-03-24 Thread Andy Chi
Public bug reported:

[Impact]
The airplane hokey doesn't work on HP new generation machines.

[Test Plan]
Press airplane hokey.

[Where problems could occur]
If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

Please refer to Bug #1955997 as well.

** Affects: oem-priority
 Importance: Critical
 Assignee: jeremyszu (os369510)
 Status: New

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1964913 originate-from-1965898 
originate-from-1966014 originate-from-1966170 stella

** Tags added: oem-priority originate-from-1966014 stella

** Tags added: originate-from-1965898

** Tags added: originate-from-1964913

** Tags added: originate-from-1966170

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

** Changed in: oem-priority
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966179

Title:
  The airplane hotkey does not work on lots of HP platforms

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  [Where problems could occur]
  If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

  Please refer to Bug #1955997 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966179/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966179] Re: The airplane hotkey does not work on lots of HP platforms

2022-03-25 Thread Andy Chi
Install #comment #1 on 202203-30011, 202203-30008, 202203-30005,
202203-30004, 202203-30029, 202203-30030, 202203-30050 and 202203-30054.
Will test it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966179

Title:
  The airplane hotkey does not work on lots of HP platforms

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  [Where problems could occur]
  If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

  Please refer to Bug #1955997 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966179/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] [NEW] Add mic mute key for HP Elite x360 series

2022-03-29 Thread Andy Chi
Public bug reported:

Upstream commit:
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

[Impact]

 * User can't use mic mute key if they buy Elite x360 G9 series.

[Test Plan]

 * Test mic mute key on Elite x360 G9 series.


[Where problems could occur]

 * This change adds key event mapping in hwdb, which won't impact other
hardware.

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1965919 originate-from-1966013 stella

** Tags added: oem-priority originate-from-1965919 stella

** Tags added: originate-from-1966013

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-03-29 Thread Andy Chi
** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-03-30 Thread Andy Chi
Upload debdiff for focal

** Patch added: "systemd_245.4-4ubuntu3.17.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967038/+attachment/5575033/+files/systemd_245.4-4ubuntu3.17.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-03-30 Thread Andy Chi
Upload debdiff for jammy

** Patch added: "systemd_249.11-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967038/+attachment/5575035/+files/systemd_249.11-0ubuntu3.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-03-30 Thread Andy Chi
Upload debdiff for impish

** Patch added: "systemd_248.3-1ubuntu8.5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967038/+attachment/5575034/+files/systemd_248.3-1ubuntu8.5.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2022-04-20 Thread Andy Chi
** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-04-25 Thread Andy Chi
Enable -proposed pocket on Elite x360 machine which is focal distribution.
Install 245.4-4ubuntu3.17 and mic mute key works as expected.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-04-25 Thread Andy Chi
Enable -proposed pocket on Elite x360 machine which is jammy distribution.
Install 249.11-0ubuntu3.1 and mic mute key works as expected.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-04-25 Thread Andy Chi
Enable -proposed pocket on Elite x360 machine which is impish distribution.
Install 248.3-1ubuntu8.6 and mic mute key works as expected. I manually install 
5.14.0-1033-oem on Elite x360 G9 to make the audio work.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-04-26 Thread Andy Chi
** Changed in: oem-priority
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1967038

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode

2023-05-15 Thread Andy Chi
** Changed in: oem-priority
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1990089

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #22 0x7fcae0743293 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #23 0x7fcadf8d0849 in meta_context_run_main_loop () from 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #24 0x55773f1a4f12 in ?? ()
  #25 0x7fcadf429d90 in __libc_start_call_main 
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1, 
argv=argv@entry=0x7fffc54053e8) at ../sysdep

[Touch-packages] [Bug 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS

2023-06-14 Thread Andy Chi
** Also affects: modemmanager (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/2023746

Title:
  [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Jammy:
  New

Bug description:
  [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS

  [ Impact ]
  The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID 
(0x311/0x312) information.
  Fwupd can't base on modemmanager to identify the modem for supporting
  WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy.
  (lp: #2019555)

  [ Test Plan ]

  Under Jammy environment,
  check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN 
LVFS on the target platform
  $ fwupdmgr refresh --force
  $ sudo fwupdmgr install
  # Select EM05-G/EM05-CN

  [ Where problems could occur ]

  The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4
  1. 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453
  2. 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63

  The Lunar and Mantic already working with modemmanager v1.20.4.
  The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic.

  The change parts just only add VID/PIDs for Quectel's new modems under
  the Quectel plugin.

  [ Other Info ]

  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2023746/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp