[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in Mutter:
  New
Status in OEM Priority Project:
  Triaged
Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

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


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

[Desktop-packages] [Bug 2009767] Re: external HDMI monitor is laggy on NV reverse PRIME system

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2009767

Title:
  external HDMI monitor is laggy on NV reverse PRIME system

Status in OEM Priority Project:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  [Summary]
  When the graphic mode is on-demand mode and plug in the monitor to HDMI port, 
there are two issue occures:
  1. External monitor's screen is very laggy in external monitor mode only.
  2. External monitor's screen sometimes (~50%) will be blak in join display 
mode.

  [Steps to reproduce]
  1. Boot in OS
  2. Plug in the external monitor in HDMI port
  3. Find the cursor moving in external monitor is laggy

  [Additional information]
  Feedback from NV:

  An NVIDIA driver built with the features needed to get rid of the laggy 
monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix 
the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it 
was first included in the 1.21.1.4 release.
  Since the older X servers crash, NVIDIA deliberately does a version check in 
the driver and enables these features for Xorg servers that are known to work, 
i.e. 1.21.1.4 or higher.

  This unfortunately prevents backporting the fix to 1.21.1.3.
  Engineering has chosen this approach since a crash is worse than the
  low FPS lag and the user might lose work merely by plugging/unplugging
  displays. If it was about a performance degradation, slight
  corruption, or something non-fatal, we wouldn't need to check Xorg
  version

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


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

[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor

[Rex Tsai]

Changed the bug importance of oem-priority to Critical, since it impacts
the user experience on Wayland and failed on Ubuntu Desktop
certification requirement.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in Mutter:
  New
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

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


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

[Desktop-packages] [Bug 1985057] Re: Camera output freeze when using pipewiresrc

[Rex Tsai]

** Changed in: oem-priority
   Status: Fix Released => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/1985057

Title:
  Camera output freeze when using pipewiresrc

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Jammy:
  Triaged

Bug description:
  [Impact]
  On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck 
on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can 
reproduce it too.

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
     hardware list:
     a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
     b. 0c45:6747 Microdia Integrated_Webcam_HD
     c. 0c45:6a14 Microdia Integrated_Webcam_HD
     d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
     e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
     f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
     g. 0408:5483 Quanta Computer, Inc. HP HD Camera
     h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
     i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
     j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
  2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
  3. $ sudo reboot
  4. Check if gst-launch-1.0 work
     a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest 
gst-launch-1.0 command
     b. $ gst-launch-1.0 pipewiresrc path= !  ! decodebin ! 
videoconvert ! glimagesink
     c. Check if the result ok
  5. Check the screencast function by pressing 'prt sc'
     a. the screenshot of all screen/selected region should work good
     b. the screenrecord of all screen/selected region should work good
  6. Check that video recording in gnome-shell works
     - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, 
verify that there is a new entry in ~/Video
  7. Check that screen sharing is working
     - go to settings, screen sharing and enable the feature
     - try to connect using rdp/vnc from another client

  do those steps under wayland and unset X

  [Where problems could occur]
  The patches try to dequeue the shared buffer, instead of pool buffer to 
prevent the pool buffer being corrupted. it might cause some camera preview 
failed if shared buffer is corrupted.
  It is in upstream from 0.3.52 to 0.3.56, and there is no regression found,
  so the risk is low.

  [Other Info]
  Upstream commits:
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f

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


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

[Desktop-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

[Rex Tsai]

@seb

Sorry, I did not see the modemmanager (1.20.0-1ubuntu1) in jammy-proposed, 
would you please confirm the process? 
 
% rmadison modemmanager
 modemmanager | 1.0.0-2ubuntu1| trusty   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.0.0-2ubuntu1.1  | trusty-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.4.12-1ubuntu1   | xenial   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.4-1ubuntu0.16.04.1| xenial-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.8-2ubuntu1| bionic   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.10.0-1~ubuntu18.04.2| bionic-updates   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.12.8-1  | focal| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1~ubuntu20.04.1| focal-updates| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1  | jammy| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.19~git20220905-0ubuntu2 | kinetic  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1~ubuntu22.10.1| kinetic-proposed | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1ubuntu1   | lunar| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x


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

** Changed in: oem-priority
 Assignee: (unassigned) => Yao Wei (medicalwei)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1950282

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Rex Tsai]

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

** Changed in: oem-priority
   Status: Triaged => Won't Fix

** Changed in: oem-priority
   Status: Won't Fix => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1994027

Title:
  Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
  Fix Committed
Status in XServer:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  [Impact]
  Users using touch screen could not move windows with 'Drag-n-drop'.
  This SRU fixes the issue.

  [Test Plan]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen

  Expected: Both finger touch and wacom pen work normally.

  Actual: Wacom Pen works normally, finger touch can not move the
  windows.

  [Where problems could occur]
  It's a regression of upstream packages, 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866

  It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.

  [Version]
  xserver-xorg-core 2:21.1.3-2ubuntu2.2

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


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

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1994027

Title:
  Can't move window by drag and drop by using touch screen

Status in Mutter:
  New
Status in OEM Priority Project:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  [Summary]
  For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.

  [Steps to reproduce]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder
  4. Drag-n-drop the folder with finger touch
  5. Drag-n-drop the folder with the Wacom Pen

  [Expected result]
  Both finger touch and wacom pen work normally.

  [Actual result]
  Wacom Pen works normally, finger touch can not move the folder.

  [Failure rate]
  100%

  [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop`
  output]

  [Other Information]
  xorg  1:7.7+23ubuntu2
  mutter-common 42.2-0ubuntu1
  gnome-shell 42.4-0ubuntu0.22.04.1

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


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

[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland

[Rex Tsai]

** Changed in: oem-priority
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Confirmed
Status in gnome-shell source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Users using desktop PC is not able to switch monitor mode between mirrored 
and joined mode using Super-P or keyboard shortcut.  This SRU fixes the issue.

  [Test Plan]
  1. Use a desktop PC and start GNOME 3
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  Expected: Display Switcher popup should appear

  Actual: Display Switcher does not popup

  [Where problems could occur]
  Although this change is minimal, the impact should be only on switching 
display mode using the shortcut.

  [Version]
  gnome-shell42.2-0ubuntu0.2
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland

[Rex Tsai]

** Changed in: gnome-shell (Ubuntu Jammy)
 Assignee: Yao Wei (medicalwei) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  In Progress
Status in gnome-shell source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Users using desktop PC is not able to switch monitor mode between mirrored 
and joined mode using Super-P or keyboard shortcut.  This SRU fixes the issue.

  [Test Plan]
  1. Use a desktop PC and start GNOME 3
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  Expected: Display Switcher popup should appear

  Actual: Display Switcher does not popup

  [Where problems could occur]
  Although this change is minimal, the impact should be only on switching 
display mode using the shortcut.

  [Version]
  gnome-shell42.2-0ubuntu0.2
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1831039

Title:
  When using Wayland, the onscreen keyboard does not open in text inputs
  for non-GTK applications such as Firefox or Chrome

Status in OEM Priority Project:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  When using wayland - onscreen keyboard not open in text inputs in many
  applications such as firefox or chrome.

  Ubuntu 18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-06-09 (1455 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=cs_CZ.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-50-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
https://bugs.launchpad.net/bugs/1965901

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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

[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1957094

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Impish:
  Triaged
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Desktop-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1940377

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  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.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
   Importance: Low => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1940377

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  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.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1946476

Title:
  New on-demand default causes RTD3 never to be enabled

Status in OEM Priority Project:
  New
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Incomplete
Status in nvidia-prime source package in Impish:
  Fix Released

Bug description:
  [Steps to reproduce]
  1. Install 20.04.3 with "Third-party packages" on a system which containing a 
RTD3 supported nvidia card.
  2. After the installation, press enter to reboot system
  3. prime-select query

  [Expected result]
  on-demand

  [Actual result]
  performance

  ---

  It's because ubiquity launches `ubuntu-drivers install --packages-list
  ...` in live system but install each package to target storage.

  When installing nvidia-prime, the preinst set "on" to "/etc/prime-
  discrete" which will be referred by gpu-manager. The gpu-manager will
  set to performance mode.

  After confirming with Alberto on Mattermost, since we don't have a
  nvidia driver which lower than 450 version since focal.

  I think we are ok to switch to on-demand mode.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode combined two features which are GPU offloading and RTD3. 
Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and 
only have GPU offloading feature.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)

[ Alberto Milone ]
* prime-select:
  - Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
is not available.
  - Don't check the current profile when setting
a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
not available.

  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium

[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)

[ Alberto Milone ]
* prime-select:
  - Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
is not available.
  - Don't check the current profile when setting
a profile (LP: #1946476).

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


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

[Desktop-packages] [Bug 1865838] Re: no error displayed on failed fingerprint authentication

[Rex Tsai]

** Changed in: oem-priority
   Status: New => Fix Committed

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1865838

Title:
  no error displayed on failed fingerprint authentication

Status in gdm:
  New
Status in OEM Priority Project:
  Fix Released
Status in fprintd package in Ubuntu:
  Invalid
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in fprintd source package in Focal:
  Invalid
Status in gdm3 source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  No fingerprint errors are exposed on fingerprint login failures.

  from journalctl, gdm-fingerprint shows error there after retried 5
  times of fingerprint login failed, so I open this issue here.

  [ Test case ]

  1. enroll fingerprint for your right index finger.
  2. logout
  3. login and try login by incorrect finger e.g. middle finger
  4. Each time the wrong finger is used an error is shown
  5. After 3 times retries, an authentication error is shown, suggesting
     to use another method.

  [ Regression potential]

  Wrong errors are shown during both fingerprint auth and other kinds of 
authentications.
  Password failures aren't properly exposed. Verification can't restart on 
error.

  Password authentication doesn't work anymore for users with no
  enrolled prints (as per LP: #1915570)

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 15:32:00 2020
  InstallationDate: Installed on 2020-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200301)SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1875015

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in Nouveau Xorg driver:
  Unknown
Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Hirsute:
  In Progress
Status in xorg-server source package in Impish:
  Fix Released

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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

[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1942788

Title:
  Nvidia doesn't support RTD3 on non-laptops

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress

Bug description:
  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.

  https://github.com/tseliot/ubuntu-drivers-common/issues/55

  We need to check chassis type before enabling RTD3.

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


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

[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1942789

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm  

  # is supported, enable it 

  if (os.path.isfile('/run/nvidia_runtimepm_supported') and 

  os.path.isfile('/usr/bin/prime-select')): 

  print('Trying to select the on-demand PRIME profile') 

  
  try:  

  subprocess.call(['prime-select', 'on-demand'])

  except:   

  pass  



  # Create the override file for gpu-manager

  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:  

  f.write('# File created by ubuntu-drivers\n')
  ```

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


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

[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1943816

Title:
  "ubuntu-drivers install" needs to be used when installing nvidia-
  driver if enabling "third-party packages"

Status in OEM Priority Project:
  Confirmed
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  ubiquity calls
  ```
  ubuntu-drivers install $FREEONLY $NOOEM --package-list 
/run/ubuntu-drivers.autoinstall
  ```
  to generate package list during live system but "ubuntu-drivers install" not 
only install packages but also create some config files for switching nvidia 
mode (e.g. on-demand) and change the runtime config as well (e.g. modify the 
iniramfs).

  Thus, not only package list needs to be referred but also the
  configuration.

  ---

  In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to 
install package. It also skipping the nvidia-mode changing (made by 
ubuntu-drivers install).
  ```
  $ cat ubiquity/target-config/31ubuntu_driver_packages
  #!/bin/sh
  set -e

  # install all packages that "ubuntu-drivers autoinstall" installed into the
  # live system. Ubiquity calls this with --package-list 
/run/ubuntu-drivers.autoinstall

  PKGLIST=/run/ubuntu-drivers.autoinstall
  [ -e $PKGLIST ] || exit 0

  for p in `cat $PKGLIST`; do
  apt-install $p
  done
  ```

  ---

  We need to use a same approach to make sure the nvidia mode is same on
  a same system (either all handing by ubuntu-drivers install or change
  the logic to maintainer script in each package).

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


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

[Desktop-packages] [Bug 1941724] Re: ubuntu-drivers install nvidia driver will be on-demand but installation from software-properties is performance mode

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1941724

Title:
  ubuntu-drivers install nvidia driver will be on-demand but
  installation from software-properties is performance mode

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  [steps to reproduce]
  1. Find a nvidia card which supports RTD3
  2. Plug this card in a desktop
  3. Install Ubuntu 20.04 focal on this desktop and connect to a monitor from 
dgpu
  4. Select "Install third-party software for graphics and WiFi hardware and 
additional media formats"
  5. After installation and boot into OS
  6. $ prime-select query
     nvidia
  7. Remove nvidia driver
  8. $ ubuntu-drivers install
     $ prime-select query
     on-demand

  In addition to use software-properties after installing stock ubuntu,
  selecting nvidia-driver-470 is also performance mode.

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


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

[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver

[Rex Tsai]

** Changed in: oem-priority
 Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1920096

Title:
  Cursor bleeds on the platform with Mali armsoc driver

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  The cursor bleeds because of the bug in xorg which does not refresh the 
sprite background. (LP: #1911479)
  The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu).

  [Test Case]

  Check if cursor is still bleeding with the patched xorg-server

  [ Regression potential ]

  The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver.
  It won't impact other platforms.

  ---
  Xilinx is trying to upstream the patch. It's still under review.
  https://lists.x.org/archives/xorg-devel/2021-March/058672.html

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

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

[Desktop-packages] [Bug 1856032] Re: Removable media icon stays on the dock after eject.

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1856032

Title:
  Removable media icon stays on the dock after eject.

Status in OEM Priority Project:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) Dock
  3) I placed a DVD in the optical drive. An optical disc with a DVD tag 
appeared on the dock. I pressed the button on the optical drive to open it. I 
removed the disc and pressed in the tray. The icon should have disappeared from 
the dock.
  4) The icon did NOT disappear from the dock.

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

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

[Desktop-packages] [Bug 1925779] Re: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port.

[Rex Tsai]

** Tags added: hwe-audio

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1925779

Title:
  [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No
  sound at all when the audio output from HDMI port.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound at all when the audio output from HDMI port.

  [Steps to reproduce]
  1. Install the daily build image on Lenovo T14s-AMD 
  2. Login the system
  3. Connect the HDMI port with a Monitor
  4. Select the 'Output Device' is HDMI
  5. Try to play sound from the monitor

  [Actual result]
  No sound at all when the audio output from HDMI port.
  The internal speaker works normally.

  [Test image]
  http://cdimage.ubuntu.com/ubuntu/daily-live/current/hirsute-desktop-amd64.iso

  [Test Device]
  https://certification.canonical.com/hardware/202006-27964

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  u  1424 F pulseaudio
   /dev/snd/controlC1:  u  1424 F pulseaudio
   /dev/snd/controlC0:  u  1424 F pulseaudio
   /dev/snd/pcmC0D0c:   u  1424 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 23 06:18:01 2021
  InstallationDate: Installed on 2021-04-23 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  u  1424 F pulseaudio
   /dev/snd/controlC1:  u  1424 F pulseaudio
   /dev/snd/controlC0:  u  1424 F pulseaudio
   /dev/snd/pcmC0D0c:   u  1424 F...m pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET55T(1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UHZ5DXUS
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET55T(1.24):bd09/15/2020:br1.24:efr1.24:svnLENOVO:pn20UHZ5DXUS:pvrThinkPadT14sGen1:rvnLENOVO:rn20UHZ5DXUS:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UHZ5DXUS
  dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925779/+subscriptions

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

[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver

[Rex Tsai]

I believe Timo and Ethan are working on SRU the changes back to focal
for an OEM project.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1920096

Title:
  Cursor bleeds on the platform with Mali armsoc driver

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  The cursor bleeds because of the bug in xorg which does not refresh the 
sprite background. (LP: #1911479)
  The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu).

  [Test Case]

  Check if cursor is still bleeding with the patched xorg-server

  [ Regression potential ]

  The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver.
  It won't impact other platforms.

  ---
  Xilinx is trying to upstream the patch. It's still under review.
  https://lists.x.org/archives/xorg-devel/2021-March/058672.html

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

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

[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver

[Rex Tsai]

** Tags added: xilinx

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1920096

Title:
  Cursor bleeds on the platform with Mali armsoc driver

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  [Impact]

  The cursor bleeds because of the bug in xorg which does not refresh the 
sprite background. (LP: #1911479)
  The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu).

  [Test Case]

  Check if cursor is still bleeding with the patched xorg-server

  [ Regression potential ]

  The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver.
  It won't impact other platforms.

  ---
  Xilinx is trying to upstream the patch. It's still under review.
  https://lists.x.org/archives/xorg-devel/2021-March/058672.html

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

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

[Desktop-packages] [Bug 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libwacom in Ubuntu.
https://bugs.launchpad.net/bugs/1921991

Title:
  [SRU] Support isdv4-aes stylus group and multiple AES stylus
  definitions

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

Bug description:
  [Impact]

   * There are lots of stylus couldn't be used on Lenovo's platform, our
  OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga
  Gen5, ThinkPad P1 G3.

   * I reviewed and tested the below patches from upstream. It could
  support the stylus very well on P15, P1 or X1 Yoga.

   * a864679 - Add multiple AES stylus definitions 
     I applied into libwacom2 1.3-2ubuntu1, no errors.

   * 8652aa3 - Add isdv4-aes stylus group to all AES sensors
    I tried to apply this patch, but there are not 'data/isdv4-48ca.tablet' and 
'data/isdv4-48ce.tablet', it failed for these two files.

   * ba02abf - Add ISDv4 51e9 (Lenovo ThinkPad P15 Gen 1) (#325)

  [Test Plan]

   * Need your laptop have AES stylus, check the pen setting at gnome-
  control-center when the pen touch the screen. It could not
  set/customize the stylus, such as the second button as right click.

   * After updated the new packages with these patches, you could
  customize the stylus at gnome-control-center.

  [Where problems could occur]

   * It only changes the data/ parts to support more stylus from
  upstream, so it's low risk.

  [Other Info]

   * Related bug:
  https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059

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

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

[Desktop-packages] [Bug 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libwacom in Ubuntu.
https://bugs.launchpad.net/bugs/1869059

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

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

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1891974] Re: [06cb:00be] Synaptics fingerprint reader is not supported

[Rex Tsai]

The [06cb:00be] is confirmed non-supported in v1.90.7[1], Closing this
issue to won't fix.

[1]
https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/v1.90.7/libfprint
/fprint-list-udev-rules.c#L47


** Changed in: oem-priority
   Status: Confirmed => Won't Fix

** Changed in: libfprint (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1891974

Title:
  [06cb:00be] Synaptics fingerprint reader is not supported

Status in OEM Priority Project:
  Won't Fix
Status in libfprint package in Ubuntu:
  Won't Fix

Bug description:
  We already supported Synaptics 06cb:00bd fingerprint recently, but can
  not support another ID yet: Synaptics 06cb:00be

  Tested on Ubuntu 20.04.1.
  Platform with this chip 
https://certification.ubuntu.com/catalog/component/06cb:00be

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

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

[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1920096

Title:
  Cursor bleeds on the platform with Mali armsoc driver

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  [Impact]

  The cursor bleeds because of the bug in xorg which does not refresh the 
sprite background. (LP: #1911479)
  The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu).

  [Test Case]

  Check if cursor is still bleeding with the patched xorg-server

  [ Regression potential ]

  The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver.
  It won't impact other platforms.

  ---
  Xilinx is trying to upstream the patch. It's still under review.
  https://lists.x.org/archives/xorg-devel/2021-March/058672.html

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

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

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

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
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:
  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/oem-priority/+bug/1918855/+subscriptions

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

[Desktop-packages] [Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless

[Rex Tsai]

Macro do we have a plan when we can port the patches or upgrade to
3.36.8?

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
 Assignee: (unassigned) => Alex Tu (alextu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1905825

Title:
  [SRU] Disable CRTCs when system becomes headless

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

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

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

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

[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1915003

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  In Progress
Status in nvidia-prime source package in Groovy:
  In Progress
Status in nvidia-settings source package in Groovy:
  In Progress

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions

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

[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic

[Rex Tsai]

** Tags added: originate-from-1910630 sutton

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1908167

Title:
  [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be
  selected automatically if there is no internal mic

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

Bug description:
  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.

  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.

  [Test]
  With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.

  With the new proposed package, on those Dell AIO, plug a headset, open
  the gnome sound setting, the headset-mic is selected automatically,
  use the headset-mic to record the sound, the sound could be recorded
  and the sound quality is good.

  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

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

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

[Desktop-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack

[Rex Tsai]

** Tags added: oem-priority originate-from-1912136 sutton

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1896098

Title:
  Lenovo P1G3 - unable to select system speakers when headset plugged
  into audio jack

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I suspect this is a pulseaudio or alsa bug.

  Our test team reported this:
  1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS .
  2. Boot system.
  3. Play audio or video file.
  4. Open Settings > Sound.
  5. Hot attach headset.
  6. Notice that headset is selected as output device in sound settings and 
sound can be heard from headset => EXPECTED
  7. While playback, select Internal Speaker as output device => KEYPOINT
  9. Notice:SUT havo no sound from Internal Speakers => PROBLEM

  I was able to confirm this - it seems with the headphones connected
  that I can't select the system speakers. If I don't have headphones
  connected I can switch between dock audio and system speakers
  correctly - so it's just related to the audio jack

  Thanks
  Mark

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

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

[Desktop-packages] [Bug 1905600] Re: Support fingerprint identification in the driver of Synaptics fingerprint reader

[Rex Tsai]

** Changed in: oem-priority
   Status: Fix Released => In Progress

** Changed in: oem-priority
 Assignee: Shengyao Xue (xueshengyao) => Bin Li (binli)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1905600

Title:
  Support fingerprint identification in the driver of Synaptics
  fingerprint reader

Status in OEM Priority Project:
  In Progress
Status in libfprint package in Ubuntu:
  Fix Released
Status in libfprint source package in Focal:
  Fix Committed
Status in libfprint source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  On Ubuntu 20.04, with Synaptics fingerprint reader, users can use one
  fingerprint to login system, but if users add more fingerprints, they
  still can only one of those to login, other fingerprints do not work.

  To fix this issue, we need support fingerprint identification in the driver 
of Synaptics fingerprint reader, by backport this libfprint commit to Focal:
  https://gitlab.freedesktop.org/libfprint/libfprint/commit/e27b65c9

  [Test Case]

  I tried backport the commit above to libfprint
  (1:1.90.2+tod1-0ubuntu1~20.04.2) in Focal and tested on 3
  ThinkPads(both use the 06cb:00bd Synaptics fingerprint reader), the
  multiple fingerprints works well.

  We have other OEM platforms with Synaptics fingerprint reader, we can
  use it to validate the changes if needed.

  [Regression Potential]

  the commit comes from Synaptics' engineer, just affects one file:
  libfprint/drivers/synaptics/synaptics.c, and only add identification
  support in that file, so the regression potential should be low.

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

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

[Desktop-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack

[Rex Tsai]

** Tags added: hwe-audio

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1896098

Title:
  Lenovo P1G3 - unable to select system speakers when headset plugged
  into audio jack

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I suspect this is a pulseaudio or alsa bug.

  Our test team reported this:
  1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS .
  2. Boot system.
  3. Play audio or video file.
  4. Open Settings > Sound.
  5. Hot attach headset.
  6. Notice that headset is selected as output device in sound settings and 
sound can be heard from headset => EXPECTED
  7. While playback, select Internal Speaker as output device => KEYPOINT
  9. Notice:SUT havo no sound from Internal Speakers => PROBLEM

  I was able to confirm this - it seems with the headphones connected
  that I can't select the system speakers. If I don't have headphones
  connected I can switch between dock audio and system speakers
  correctly - so it's just related to the audio jack

  Thanks
  Mark

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

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

[Desktop-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[Rex Tsai]

Added upstream issue link in the description for referenc - platform:
add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status check (!597) ·
Merge Requests · NetworkManager / NetworkManager · GitLab -
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639


** Description changed:

  [Impact]
  
   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).
  
   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.
  
   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The
  driver will manager itself.) When the network-manager managers the wake-
  on-LAN, all of the Wi-Fi functions will be lost after the OS resumed
  from suspend.
  
  [Test Case]
  
   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend
  
   After resume from suspend, the Wi-Fi function still is normal.
  
   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
  
  [Regression Potential]
  
   * This patch modifies the wake on lan parameters, please test that the
  corresponding feature still works fine with the different configuration
  values.
  
-  1. Magic packet test:
-   Set Wake on Wireless to off
-   Send magic packet to the system
-   Ensure it does not wake up
+  1. Magic packet test:
+   Set Wake on Wireless to off
+   Send magic packet to the system
+   Ensure it does not wake up
  
-   Set Wake on Wirless to on
-   Send magic packet to the system
-   Ensure it does wake up
+   Set Wake on Wirless to on
+   Send magic packet to the system
+   Ensure it does wake up
  
-  2. Wi-Fi function test after resumed from suspend:
-   After resume from suspend, the Wi-Fi should work normally.
-   Scan APs.
-   Connect to an AP.
+  2. Wi-Fi function test after resumed from suspend:
+   After resume from suspend, the Wi-Fi should work normally.
+   Scan APs.
+   Connect to an AP.
  
  [Other Info]
  
-  * None
+  * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
+ check (!597) · Merge Requests · NetworkManager / NetworkManager · GitLab
+ -
+ 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1891632

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi function still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / NetworkManager ·
  

[Desktop-packages] [Bug 1893719] Re: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF

[Rex Tsai]

** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1893719

Title:
  Request for adding support for Synaptics fingerprint reader sensors:
  0xE9 and 0xDF

Status in OEM Priority Project:
  Fix Released
Status in libfprint package in Ubuntu:
  Fix Released
Status in libfprint source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * We were advised by Synaptics to upgrade the existing libfprint in
  the archive to include sensor support for 0xE9 and 0xDF as highlighted
  in the following commits:

  
https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a

  [Test Case]

   * We have several OEM platforms with these Synaptics sensors enabled
  with Focal and they can be used to validate these changes.

  [Regression Potential]

   * Regression potential for an updated libfprint with these new PIDs
  is low

  [Other Info]

   None

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

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

[Desktop-packages] [Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button/menu does nothing

[Rex Tsai]

** Tags added: originate-from-1895501 stella

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715602

Title:
  ubiquity-dm / Install Ubuntu - Power button/menu does nothing

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Artful Desktop 20170907

  In ubiquity-dm and 'Install Ubuntu' the power button does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity 17.10.6
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 09:55:57 2017
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rex Tsai]

Upstream found a regression[1] with the new patch in #128, Jeremy will
review and re-test the solution in focal before asking for sponsorship.

[1] Multiple regressions in multi-user environments since 3.36.2 (#602)
· Issues · GNOME / gdm · GitLab -
https://gitlab.gnome.org/GNOME/gdm/-/issues/602


** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #602
   https://gitlab.gnome.org/GNOME/gdm/-/issues/602

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  Triaged
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-session package in Ubuntu:
  Confirmed
Status in grub2 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards (with nvidia-driver-440), enable 
auto-login (either during installation or after installation) will fail (either 
stuck in gdm login screen and not able to login even typing correct password).

  [ Test Case ]
  Here are two scenario of auto login with groovy (20.10) daily build[1]:

  1) Checked "Install third-party software" (e.g. nvidia-driver) with
  enabling "Login automatically" during installation.

  2) Install groovy daily build with default options, after installation 
completed:
  2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
  2.2) Enable "Login automatically" from system settings.

  Then reboot.

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) 
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] 
and it works good. It passed the 30 times reboot stress test by using 
stress/reboot_30 from checkbox.

  [1] sha256sum: 
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
  [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4
  [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801

  ---

  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: 

[Desktop-packages] [Bug 1891974] Re: Can not support Synaptics 06cb:00be fingerprint

[Rex Tsai]

** Description changed:

  We already supported Synaptics 06cb:00bd fingerprint recently, but can
  not support another ID yet: Synaptics 06cb:00be
  
  Tested on Ubuntu 20.04.1.
+ Platform with this chip 
https://certification.ubuntu.com/catalog/component/06cb:00be

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: libfprint (Ubuntu)
   Importance: Undecided => Wishlist

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1891974

Title:
  Can not support Synaptics 06cb:00be fingerprint

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

Bug description:
  We already supported Synaptics 06cb:00bd fingerprint recently, but can
  not support another ID yet: Synaptics 06cb:00be

  Tested on Ubuntu 20.04.1.
  Platform with this chip 
https://certification.ubuntu.com/catalog/component/06cb:00be

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

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

[Desktop-packages] [Bug 1892698] [NEW] [138A:003A] Validity Sensors, Inc. VFS495 Fingerprint Reader is currently not supported by libfprin

[Rex Tsai]

Public bug reported:

It's used on a certified paltform, but it's not been supported by
libfprint v1.90.2 nor IHV.

[1] Validity Sensors, Inc. VFS495 Fingerprint Reader -
https://certification.ubuntu.com/catalog/component/138a:003f

** Affects: oem-priority
 Importance: Low
 Status: New

** Affects: libfprint (Ubuntu)
 Importance: Wishlist
 Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: libfprint (Ubuntu)
   Importance: Low => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1892698

Title:
  [138A:003A] Validity Sensors, Inc. VFS495 Fingerprint Reader is
  currently not supported by libfprin

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

Bug description:
  It's used on a certified paltform, but it's not been supported by
  libfprint v1.90.2 nor IHV.

  [1] Validity Sensors, Inc. VFS495 Fingerprint Reader -
  https://certification.ubuntu.com/catalog/component/138a:003f

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rex Tsai]

** Tags added: originate-from-1892498

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in grub2 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards, auto-login will fail due to the 
old vt-handoff patch in grub2.

  [ Test Case ]
  1. Boot ubuntu into desktop environment.
  2. Enabled auto login in System->Users
  3. Reboot the system

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Low, the patch just removes vt.handoff part in grub2 package, and I can't 
find any regression in several runs of stress tests.

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801

  ---

  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Desktop-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04

[Rex Tsai]

** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1892288

Title:
  Comet Lake PCH-H RAID not support on Ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
  { PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */

  If Thinkstation P340 configured as RAID mode, It can not find any RAID volume 
disk.
  please update such support. Thanks.

  Regards,
  Jiqi.

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

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

[Desktop-packages] [Bug 1837962] Re: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while

[Rex Tsai]

** No longer affects: oem-priority

** Tags removed: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1837962

Title:
  Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a
  while

Status in libinput:
  Fix Released
Status in libinput package in Ubuntu:
  Fix Released
Status in libinput source package in Bionic:
  Fix Released
Status in libinput source package in Disco:
  Fix Released
Status in libinput source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  4.18+ kernel with Ubuntu 18.04.
  libinput 1.10.4-1
  xserver-xorg-input-libinput 0.27.1-1
  tap-to-click is on by default.
  After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no 
response when tapping.

  [Fix]
  libinput detect these taps as palm, so permanently disable tap-to-click.
  upstream patch of libinput already fixed this issue:

  commit 237ebb7cc4e9bf035891176acb08b1bf558ee989
  Author: Peter Hutterer 
  Date:   Mon Jun 25 14:50:22 2018 +1000

  touchpad: don't disable tapping on MT_TOOL_PALM
  
  The tapping code can handle palm states now, so there is no need to 
disable
  tapping altogether when a tool-based palm is detected.
  
  Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65
  
  Signed-off-by: Peter Hutterer 

  [Test]
  Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for 
thousands of times.
  touchpad taping OK.

  [Regression Potential]
  Low, upstream fix, tested OK.

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

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

[Desktop-packages] [Bug 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1847219

Title:
  HDMI audio lost function after the dGPU did runtime suspend. (AMD RX
  580)

Status in OEM Priority Project:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  On Dell Precision 7740, after installed amdgpu-pro 19.10-793418, the
  HDMI audio will lose function after the dGPU did runtime suspend.

  How to check the AMD dGPU is in runtime suspend:
   $ lspci -s 01:00.0 -xxvv
  When the AMD dGPU is in runtime suspend, all of the registers will be 0xf.

  Release: 18.04 LTS
  kernel: 4.15.0-1037-oem
  amdgpu-pro: 19.10-793418

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

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

[Desktop-packages] [Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1844650

Title:
  No authentication window pops up if thunderbolt device be plugged
  before booting

Status in GNOME Shell:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  [Summary]
  In order to access the docking station resource, the system should pop up an 
authentication window after the cold boot. But, currently, no authentication 
window pops up after the cold boot. The authentication window only pops up 
after replugging it during the running state of the system.

  [Pre condition]
   - the testing thunderbolt device is not authenticated before
 - e.g. this is the 1st time you plugging this device.
 - e.g. execute `boltctl forget ${device}` to make sure target device not 
be authenticated

  [Steps to reproduce]
  1. keep the machine in the power-off state.
  2. Plugin the docking station(TB16/TB18)
  3. Boot up the system
  4. Check if an authentication window pops up after Ubuntu desktop displayed

  [Expected result]
  An authentication window pops up after Ubuntu desktop displayed

  [Actual result]
  No authentication window pops up after the cold boot

  [Failure rate]
  100%

  [Additional information]
  this issue can also be reproduced by  19.10 which has bolt 0.8-2 and kernel 
5.2.0-15-generic

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

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

[Desktop-packages] [Bug 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1841886

Title:
  Join Displays failed when using two external monitor of one Full HD
  and one Ultra HD

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  [Summary] Join Displays failed when using two external monitor of one
  Full HD and one Ultra HD

  [Reproduce Steps]
  1. Boot into the desktop environment with DELL DOCK - WD19 130W [1].
  2. Connect one Ultra HD (3840x2160) external monitor and one Full HD 
(1920x1080) external monitor.
  3. Press Win+P to switch to Join Displays mode.

  [Results]
  Expected: All monitors including the internal monitor can display with Full 
HD (1920x1080).
  Actual: The Ultra HD monitor can not display.

  [Additional Information]
  1. Using only Ultra HD (3840x2160) external monitor with internal Full HD 
(1920x1020) display works fine.
  2. Executing the command like `xrandr --output eDP-1 --primary --preferred 
--output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 
--mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) 

  [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products
  /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf

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

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

[Desktop-packages] [Bug 1889374] Re: Ubuntu Dock shows only one storage icon for multiple USB drivers with the same size

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1889374

Title:
  Ubuntu Dock shows only  one storage icon for multiple USB drivers with
  the same size

Status in OEM Priority Project:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Summary: Not all the USB drivers were shown on task bar

  Steps to reproduce:
  Connect multiple(more than 2) usb keys to usb ports

  Expected result:
  USB keys will be shown on the task bar on the left side of screen.

  Actual result:
  Only 2 USB key icons were shown in the task bar, but we can see all the usb 
keys in folders view, at attached screenshot.

  Ubuntu Version: 20.04.1
  gnome-shell: 3.36.3-1ubuntu1~20.04.2
  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20200609-41+sutton-newell-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-10 (49 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200609-13:40
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 [modified: 
usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override 
usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js]
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  Tags: focal third-party-packages
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1879893

Title:
  GNOME crashed when resuming from sleep in NVIDIA performance mode with
  disconnecting dell-wd19tb-dock

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid
Status in xorg-server source package in Groovy:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Groovy:
  Invalid

Bug description:
  1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, 
xserver-xorg-hwe-18.04 and nvidia-driver-440.
  2. Select the performance mode in NVIDIA settings and reboot the system.
  3. Connect dell-wd19tb-dock to the system.
  4. Connect external HDMI monitor to dell-wd19tb-dock.
  5. Open a terminal, some GUI applications and then execute `systemctl 
suspend` in the terminal.
  6. Disconnect dell-wd19tb-dock after the system fell asleep.
  7. Resume the system and login the GNOME desktop environment.

  Expected result:
  The terminal and other GUI applications will still exist.

  Actual result:
  All opened GUI applications in GNOME are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1052-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 03:31:41 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-gilly+X33
  InstallationDate: Installed on 2020-05-06 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg-server-hwe-18.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1873184

Title:
  Wired and wireless connection details have not enough height and items
  overlap

Status in gnome-control-center:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  There is a display bug when you unplug the network cable on focal.
  Please see attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions

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

[Desktop-packages] [Bug 1879876] Re: Screen should not rotate automatically on a laptop

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1879876

Title:
  Screen should not rotate automatically on a laptop

Status in IIO Sensor Proxy:
  Unknown
Status in OEM Priority Project:
  New
Status in iio-sensor-proxy package in Ubuntu:
  New

Bug description:
  There are recently more machines shipped with an accelerometer to
  bring about the automatic rotation feature on pad-like or 2in1
  products. However, manufacturers sometimes share designs between
  platforms; a laptop may mount an accelerometer on its panel. The user
  experience on laptops with a fixed keyboard/touchpad that rotates
  automatically is somehow annoying, and the touchpad motion is
  confusing.

  The SMBIOS specification defines chassis type in section 7.4.1. Softwares can 
determine to rotate automatically or not by checking this value, or at least 
not to rotate on a laptop(0x09) and notebook(0x0A).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-05 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/iio-sensor-proxy/+bug/1879876/+subscriptions

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

[Desktop-packages] [Bug 1318875] Re: Airplane mode cannot save the previous status after reboot

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1318875

Title:
  Airplane mode cannot save the previous status after reboot

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  Airplane mode cannot save the previous status after reboot.

  Steps to reproduce:
  1. open network settings
  2. turn on airplane mode
  3. reboot -> issue occurs, airplane mode is off
  ---
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-daan2-precise-amd64-20140502-1
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140502-06:48
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: gnome-control-center 1:3.4.2-0ubuntu0.13.1stella1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Tags:  precise running-unity
  Uname: Linux 3.11.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu4
   gnome-bluetooth 3.2.2-0ubuntu5.1stella2
   indicator-datetime  0.3.94-0ubuntu2
  ---
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong-trusty-amd64-20140606-1
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-06-09 (7 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140606-09:30
  NonfreeKernelModules: nvidia wl
  Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1649763

Title:
  Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

Status in OEM Priority Project:
  Confirmed
Status in Unity Control Center:
  New
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  This issue is related to sound not working properly on Ubuntu when
  switching between an external display using HDMI with 4K resolution
  and the standard laptop display.

  Issue 1 - Sound only works on laptop when plugged into 4k HDMI display
  Issue 2 - Sound doesn't work when plugged removed from 4k HDMI display

  When you plug in a 4k Display that supports sound to the Dell XPS 15
  2016 model the sound only works on the laptop. Only when you go to
  Sound Settings and manually select the HDMI output for sound does the
  sound start to work on the display itself instead of the laptop.

  When you unplug the HDMI 4k display the sound doesn't work on the
  laptop. When you go to the Sound Settings dialog it only shows one
  output that is selected - if you select the same output thats already
  selected the sound starts to work again on the laptop.

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

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

[Desktop-packages] [Bug 1667222] Re: set password in "user accounts panel' won't remove user from "nopasswdlogin" in all cases

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1667222

Title:
  set password in "user accounts panel' won't remove user from
  "nopasswdlogin" in all cases

Status in OEM Priority Project:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  Step to reproduce

  1. add the current login user to "nopasswdlogin" group by
   1.1 launch "user accounts panel" in unity-control-center
   1.2 Click "Unlock" at the top right, and enter the user's password.
   1.3. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
   1.4 In the combo box at the top, select "Log in without a password". Save 
the dialog.
   1.5 Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  2. log out, and confirm password is not needed to login.
  3. launch launch "user accounts panel" in unity-control-center again.
  4. change the login user's password

  Expected behavior
  1. new user password is set without any warning message, and user is removed 
from group "nopasswdlogin".

  Current behavior
  1. system prompt "Authentication is required to change user data", and the 
only way out is press cancel.
  2. after press cancel, new user password is set, but the user is still in 
"nopasswdlogin" group. (checked by `grep nopasswdlogin /etc/group`)

  Note: this is still reproducible even use the new  unity-control-
  center in LP: #1630156.

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

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

[Desktop-packages] [Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button/menu does nothing

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715602

Title:
  ubiquity-dm / Install Ubuntu - Power button/menu does nothing

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Artful Desktop 20170907

  In ubiquity-dm and 'Install Ubuntu' the power button does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity 17.10.6
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 09:55:57 2017
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1722256

Title:
  Wifi connection status icon shows a "?" question mark when connected

Status in GNOME Shell:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=750260

  Wifi connection status icon on the top bar shows a "?" even when connected to 
a wifi network.
  ---
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-28 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.26.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1864813

Title:
  As there is not built-in speaker, and not any output, the dummy output
  in g-c-c will disappear after plug headset once.

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  The dummy output in gnome-contol-center (g-c-c) will exists if

  - no built-in speaker
  - no headphone/earphone plugged
  - using display (like VGA, DVI) without audio out is plugged.

  However, in bionic, it will disappear as the headset is plugged and selected.
  After it disappears, a reboot won't make it appear again.

  bionic:
gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6
pulseaudio: 1:11.1-1ubuntu7.4

  In Focal, dummy output won't disappear.

  focal:
    pulseaudio 1:13.0-3ubuntu2
    gnome-control-center 1:3.35.91-0ubuntu1

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

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

[Desktop-packages] [Bug 1839016] Re: Suspend process is interrupted by ALT key

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1839016

Title:
  Suspend process is interrupted by ALT key

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  When trying to suspend the system via pressing the power button in the
  system tray with ALT key pressed, it is possible to interrupt the
  system to enter sleep mode and fall back to screen lock. While trying
  to unlock the screen, the system goes to sleep immediately.

  Gnome-shell is able to suspend the system by drop-down menu in the
  system tray. By pressing ALT key or long-press the power button until
  it switches to suspend icon. The system will suspend if it is by the
  long-press power button, while with ALT key pressed, there is a
  failure rate that causes the suspend process to be interrupted.

  The second issue is that if the suspend process is interrupted, the
  locked screen is shown. While trying to unlock the screen by inputting
  password, the system will go sleeping after that.

  STEPS TO REPRODUCE:
  1. To suspend system via pressing the power button in the drop-down system 
tray with ALT key pressed.
  2. During system is going to sleep, e.g., screen going dark, emulate a key 
bounce by pressing ALT key again.

  RESULTS:
  The locked screen shows up and goes to sleep after tens of seconds. While 
trying to unlock screen, system enter suspend after unlocking successfully.

  EXPECTED RESULTS:
  The system going to sleep without a problem.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1

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

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

[Desktop-packages] [Bug 1851202] Re: Need iw 5.3 in 18.04 Bionic

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iw in Ubuntu.
https://bugs.launchpad.net/bugs/1851202

Title:
  Need iw 5.3 in 18.04 Bionic

Status in OEM Priority Project:
  New
Status in iw package in Ubuntu:
  Opinion

Bug description:
  Current iw verion in Bionic is 4.14. Need iw 5.3 for better 802.11ax
  High-Efficiency Wireless support.

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

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

[Desktop-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871329

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

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

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1351772] Re: "disable touchpad while typing" doesn't work

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1351772

Title:
  "disable touchpad while typing" doesn't work

Status in OEM Priority Project:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  When selecting "disable while typing" under the touchpad section of
  the "Mouse & Touchpad" preferences, nothing changes, the touchpad
  stays active while typing. I can rapidly type multiple characters with
  my left hand and continue to move the cursor with the touchpad with my
  right hand.

  I can see from my processlist that syndaemon is running with the
  following options:

   2185 ?S  1:31  |   \_ syndaemon -i 1.0 -t -K -R

  First, the -t option isn't what's expected with this setting, it
  should disable the touchpad entirely. Also, it doesn't seem to even do
  that correctly, as I can definitely click the touchpad while typing as
  well as moving the cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  Uname: Linux 3.14.0-997-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug  2 17:20:22 2014
  InstallationDate: Installed on 2014-04-22 (102 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647283

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]

   * It is a very bad user experience that the WiFi device is recognized
  as an Ethernet device making Ubuntu users unable to connect to WiFi
  network.

  [Test Case]

   * Find some laptop that can reduplicate this issue.
   * Keep rebooting the system until you see this issue.
   * Usually this issue can be reduplicated within 10 reboot cycles on the 
right laptop.

  [Regression Potential]

   * No trivial regression.

  [Other Info]
   
   * network-manager_1.2.6-0ubuntu0.16.04.2.debdiff (comment #8) is for xenial

  [Original Bug Description]

  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

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

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

[Desktop-packages] [Bug 1691032] Re: Some PCs still turn off the backlight by zero brightness even when the maximum brightness level is less than 100

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1691032

Title:
  Some PCs still turn off the backlight by zero brightness even when the
  maximum brightness level is less than 100

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in Unity Settings Daemon:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  Need to have fix in Bionic, better to have it in xenial.

  The minimum brightness of the laptop screen panel may not be realistic
  sometimes especially when having a problematic screen panel.

  For example, Dell Precision 5720 AIO only has 9 levels in
  /sys/class/backlight/intel_backlight/max_brightness because the wrong
  settings in VBIOS. It is an all-in-one desktop PC and there is no
  brightness hotkey to control the backlight. When we set 0 to
  /sys/class/backlight/intel_backlight/brightness, it turns off the
  panel's backlight and there is no way to brightness up the backlight
  again so we can only avoid using 0 as the minimum backlight level.

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

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

[Desktop-packages] [Bug 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1672619

Title:
  "disable touchpad while typing" doesn't work on xps 13 and some other
  laptop

Status in OEM Priority Project:
  Triaged
Status in Xserver Xorg Input Synaptics:
  Unknown
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  It's reported that there are lots of false action of touch pad as using 
keyboard on xps 13
  with the factory image.

  The factory image is based on xenial.

  One propose that install xserver-xorg-input-libinput with modification
  90-libinput.conf in /usr/share/X11/xorg.conf.d from

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  EndSection
  ...

  to

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  Option "Tapping" "on"
  Option "PalmDetection" "on"
  EndSection
  ...

  helps a lot.

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

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

[Desktop-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format

[Rex Tsai]

** Changed in: oem-priority
   Importance: High => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1882896

Title:
  cheese not recognize resolution in MJPG format

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  New
Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  reproduce step:
   - open cheese
   - open preferences -> resolution
   - only resolution from YUYV format in options

  the patches there works well and waiting for merge:
  https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1build1
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  Uname: Linux 5.6.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 15:23:02 2020
  InstallationDate: Installed on 2020-04-12 (58 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  RelatedPackageVersions:
   cheese3.34.0-1build1
   cheese-common 3.34.0-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1889378] Re: dbus method 'Sleep' not work

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1889378

Title:
  dbus method 'Sleep' not work

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  refer to https://salsa.debian.org/utopia-team/network-
  
manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157

  
  
    
  

  But the network not be deactivated after the Sleep method be called.

  steps:
   1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path 
/org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep 
true

   2.$ journal ctl ; # see the dbus method be called correctly.
  NetworkManager[843]:   [1596010870.8622] manager: sleep: sleep 
requested (sleeping: no  enabled: yes)
  NetworkManager[843]:   [1596010870.8626] device (p2p-dev-wlp0s20f3): 
state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 
'managed')
  NetworkManager[843]:   [1596010870.8632] manager: NetworkManager state 
is now ASLEEP
  NetworkManager[843]:   [1596010870.8635] audit: op="sleep-control" 
arg="on" pid=2825 uid=0 result="success"

  3. $ ping 8.8.8.8 ; # still work unexpectedly

  Note: this issue can be reproduced on the latest version of network-
  manager source : https://git.launchpad.net/network-
  manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2

  upstream bug:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/503

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

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

[Desktop-packages] [Bug 1844934] Re: screen jitter after long idle

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1844934

Title:
  screen jitter after long idle

Status in OEM Priority Project:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It's 1st time happens on my xps13 9380 with bionic + oem kernel 
4.15.0-1056-oem.
  I have updated to 1056 from 1050 for several days, this issue not happens for 
these days and not experienced it on 1050 as well. So, looks it's just randomly 
happens or I can not find a static way to reproduce it.

  I also not sure if unattended upgrade bring in some regression.

  So, my plan would be
  1. do apt full-upgrade, and if it still can be reproduce then.
  2. try mainline kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-1056.65-oem 4.15.18
  Uname: Linux 4.15.0-1056-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 00:14:35 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08af]
  InstallationDate: Installed on 2019-08-11 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1056-oem 
root=UUID=d6c42edb-0a08-49cc-89e9-fe4df2d0c5e1 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1834138

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

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

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

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1845163

Title:
  The cancel button of the paring dialog does not work during pairing a
  bluetooth keyboard

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.

  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
  2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).

  Expected: the Cancel button is work. And, the pairing is canceled normally.
  Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.

  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1845163/+subscriptions

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

[Desktop-packages] [Bug 1840416] Re: 2.4g wifi connection failed randomly during wpa re-key

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1840416

Title:
  2.4g wifi connection failed randomly during wpa re-key

Status in OEM Priority Project:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm not sure this issue caused by WIFI AP or WIFI module.
  From log, it looks the tested machine can not get new key from WIFI AP 
randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-1030.35-oem 4.15.18
  Uname: Linux 4.15.0-1030-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 16 14:51:12 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-14 (2 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IpRoute:
   default via 10.101.46.1 dev wlp2s0 proto dhcp metric 600 
   10.101.46.0/24 dev wlp2s0 proto kernel scope link src 10.101.46.198 metric 
600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Canonical-2.4GHz-g  f0a4469e-23e9-4899-a498-49a50b3a8e21  wifi  1565938016  
廿十九年八月十六日 (週五) 十四時46分56秒  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/5  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
Canonical-2.4GHz-g  f0a4469e-23e9-4899-a498-49a50b3a8e21  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1871563] Re: The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while.

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1871563

Title:
  The window is frozen 3~10 seconds when swipe, pinch and zoom on the
  google-map via touchscreen for a while.

Status in OEM Priority Project:
  New
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in focal package in Ubuntu:
  New

Bug description:
  [Summary]
  The window is frozen 3~10 seconds when swipe, pinch and zoom on the google 
map via touchscreen for a while.

  [Steps to reproduce]
  1. Use touchscreen to swipe, pinch, zoom on google map. 
(https://www.google.com/maps/)

  
  [Expected result]
  System should respond to touchscreen input

  [Actual result]
  The browser window is frozen.

  [Failure rate]
  30%

  [Additional information]
  OS: Ubuntu 20.04 daily 
  system-manufacturer: Dell Inc.
  system-product-name: XPS 13 9300
  bios-version: 1.0.6
  CPU: Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:8a56] (rev 07)
  kernel-version: 5.4.0-14-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-4:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBNEMwUAC0dAQS1HRJ4Dm5gqVJJoSYNUFQBAQEBAQEBAQEBAQEBAQEBcucAoPBgRZAwIDYAILQQAAAYKLkAoPBgRZAwIDYAILQQAAAY/gBLOEowVwpMUTEzNFIxAAACQQMyARIAAAsBCiAgAbgCAw8A4wWAAOYGBQFgYCgAqg==
   modes: 3840x2400 3840x2400
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p2 ext4   1.9T  6.5G  1.8T   1% /
   tmpfs  tmpfs   16G  133M   16G   1% /dev/shm
   /dev/nvme0n1p2 ext4   1.9T  6.5G  1.8T   1% /
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200407)
  MachineType: Dell Inc. XPS 13 9300
  Package: focal
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a1145b98-763c-4de0-9ccf-5d3a6920bca7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2020-04-08T16:27:58+08:00  2020-04-08T16:28:48+08:00  Install 
"chromium" snap
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.163 
(e7fbe071abe9328cdce4ffedac9822435fbd3656-refs/branch-heads/3987@{#1037})
  Snap.ChromiumVersion: Chromium 80.0.3987.163 snap
  Tags:  focal snap
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd12/30/2019:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1872034

Title:
  [Focal] No HDMI output through thunderbolt docking station

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I can find monitor in display list, but no output from it.
  Also, I can't switch to extend mode, it failed to apply the setting and 
switched back to mirror mode.

  [Steps]
  1. Connect a thunderbolt docking station to thunderbolt port.
  2. Connect HDMI monitor to HDMI port on the docking station.
  3. Switch mode in display setting

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 16:44:40 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1806334] Re: Thunderbolt 2 storage not auto mounted and show in file manager

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806334

Title:
  Thunderbolt 2 storage not auto mounted and  show in file manager

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in OEM Priority Project focal series:
  New
Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  OS 18.04 & 20.04

  Plug thunderbolt 2 storage device, can see the device in lsblk as
  /dev/sda (and /dev/sda1 is a ext4 partition) however I can't see it in
  file manager (check attachment, it say TBT3 in the picture, however I
  use TBT2 and I can reproduce it)

  public bug: https://github.com/storaged-project/udisks/issues/793

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

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

[Desktop-packages] [Bug 1824073] Re: USB stick isn't mounted automatically

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1824073

Title:
  USB stick isn't mounted automatically

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in udisks2 package in Ubuntu:
  Fix Released
Status in udisks2 source package in Xenial:
  New

Bug description:
  [Impact]

  USB stick isn't mounted automatically. Auto-mount function fails.

  [Test Case]

  1) Plug USB stick and check if USB stick is mounted automatically.

  2) Umount USB stick

  3) Unplug USB stick

  4) Go to 1)

  ---

  If the error message below appears, auto-mount function will fail.
  systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file 
or directory

  Error Message:

  1. when auto-mount fails:
  kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6
  systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file 
or directory
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0
  kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using 
xhci_hcd
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470

  2. when auto-mount works:
  kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 
drive_disconnected
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330
  kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using 
xhci_hcd
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 
drive_connected
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount
  udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001

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

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

[Desktop-packages] [Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1797322

Title:
  gsd-rfkill-manager fails to receive rfkill event

Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  The default encoding for GIOChannel is UTF-8, but rfkill event is
  binary data. gsd-rfkill-manager will fail to receive rfkill event if
  rfkill-idx is larger than 127.

  Settings will always shows Bluetooth is off after resume.

  The solution is to set the encoding of GIOChannel as NULL (binary
  data).

  [Test Case]

  1) Enable the -proposed repository, and install new "gnome-settings-
  daemon-schemas" and "gnome-settings-daemon"

  2) Reboot system

  3) Run suspend/resume test more than 127 times and then check if BT
  settings still works well.

  [Regression Potential]

  Low. The default encoding for GIOChannel is wrong. Just set correct
  encoding to receive rfkill event.

  ---

  The default encoding for GIOChannel is UTF-8, but rfkill event is
  binary data. If the value is invalid UTF-8, gsd-rfkill-manager will
  fail to receive rfkill event.

  Steps: Run suspend/resume Test (> 127 times)
  Failure Rate: 100%

  In some platforms, bt will be re-probed after s3. If bt is re-probed,
  rfkill-idx will increase. And, 128 is the first invalid UTF-8

  $ rfkill list
  ID TYPE DEVICE SOFT HARD
  1 wlan phy0 unblocked unblocked
  128 bluetooth hci0 unblocked unblocked

  Error Message:
  gnome-settings-daemon/plugins/rfkill/rfkill-glib.c
  gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars
  gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8
  gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8
  gsd-rfkill[2062]: event_cb: 1 read=8
  gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0
  gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0
  gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 
hard 0
  gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars
  gsd-rfkill[2062]: event_cb: 2 read=0
  gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8
  gsd-rfkill[2062]: event_cb: g_list_length=1
  gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127
  gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars
  gsd-rfkill[2062]: event_cb: 1 read=0T
  gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16
  gsd-rfkill[2062]: event_cb: g_list_length=0

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

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

[Desktop-packages] [Bug 1827030] Re: Keyboard brightness control not working

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1827030

Title:
  Keyboard brightness control not working

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Keyboard brightness control not working

  [Test Case]

  1) Go to [All Settings][Power][Keyboard brightness]

  2) Adjust keyboard brightness by sidebar

  ---

  $ cat /sys/class/leds/dell::/kbd_backlight/max_brightness
  2

  The valid value for my machine is 0, 1, and 2.
  The Power.Keyboard.Brightness property should be in percent.

  [ Regression potential ]

  Check that changing the keyboard backlight level works correctly from
  the keys as well from the settings slider

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

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

[Desktop-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1891632

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

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

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

[Desktop-packages] [Bug 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1868915

Title:
  [focal] nm-online -s --timeout=10 timeout every time

Status in MAAS:
  Invalid
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Also created bug on upstream :
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398

  
  This issue will cause "NetworkManager-wait-online.service: Failed with result 
'exit-code'."
  And cloud-init.service is counting on this service for network status.

  So this issue will finally cause MaaS deploying failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1 [modified: 
lib/systemd/system/NetworkManager-wait-online.service]
  ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8
  Uname: Linux 5.4.0-1002-oem x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Wed Mar 25 12:43:13 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09
  IfupdownConfig: source /etc/network/interfaces.d/*.cfg
  InstallationDate: Installed on 2020-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200316-08:40
  IpRoute:
   default via 192.168.101.1 dev eno1 proto static metric 100
   10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200
   169.254.0.0/16 dev eno1 scope link metric 1000
   192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 
100
  NetDevice.bonding_masters:
   Error: command ['udevadm', 'info', '--query=all', '--path', 
'/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device 
"/sys/class/net/bonding_masters": No such device

   X: INTERFACE_MAC=Error: command ['cat', 
'/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: 
/sys/class/net/bonding_masters/address: Not a directory
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   netplan-eno1  10838d80-caeb-349e-ba73-08ed16d4d666  ethernet  158577  
廿廿年三月廿五日 (週三) 十二時39分37秒  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes eno1activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/netplan-eno1.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.22.10  connected  starting  full  enabled disabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1683445] Re: E6430 brightness control not working

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1683445

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Nouveau Xorg driver:
  Won't Fix
Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in gnome-settings-daemon source package in Zesty:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Won't Fix
Status in unity-settings-daemon source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+subscriptions

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

[Desktop-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1890772

Title:
  No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc"
  is lowered to 8

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1889374] Re: Ubuntu Dock shows only one storage icon for multiple USB drivers with the same size

[Rex Tsai]

** Summary changed:

- Not all USB drives shown on Ubuntu Dock
+ Ubuntu Dock shows only  one storage icon for multiple USB drivers with the 
same size

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1889374

Title:
  Ubuntu Dock shows only  one storage icon for multiple USB drivers with
  the same size

Status in OEM Priority Project:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Summary: Not all the USB drivers were shown on task bar

  Steps to reproduce:
  Connect multiple(more than 2) usb keys to usb ports

  Expected result:
  USB keys will be shown on the task bar on the left side of screen.

  Actual result:
  Only 2 USB key icons were shown in the task bar, but we can see all the usb 
keys in folders view, at attached screenshot.

  Ubuntu Version: 20.04.1
  gnome-shell: 3.36.3-1ubuntu1~20.04.2
  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20200609-41+sutton-newell-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-10 (49 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200609-13:40
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 [modified: 
usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override 
usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js]
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  Tags: focal third-party-packages
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1889374] Re: Not all USB drives shown on Ubuntu Dock

[Rex Tsai]

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

** Changed in: oem-priority
   Importance: Medium => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1889374

Title:
  Not all USB drives shown on Ubuntu Dock

Status in OEM Priority Project:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Summary: Not all the USB drivers were shown on task bar

  Steps to reproduce:
  Connect multiple(more than 2) usb keys to usb ports

  Expected result:
  USB keys will be shown on the task bar on the left side of screen.

  Actual result:
  Only 2 USB key icons were shown in the task bar, but we can see all the usb 
keys in folders view, at attached screenshot.

  Ubuntu Version: 20.04.1
  gnome-shell: 3.36.3-1ubuntu1~20.04.2
  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20200609-41+sutton-newell-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-10 (49 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200609-13:40
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 [modified: 
usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override 
usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js]
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  Tags: focal third-party-packages
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1889374] Re: Not all USB drives shown on Ubuntu Dock

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1889374

Title:
  Not all USB drives shown on Ubuntu Dock

Status in OEM Priority Project:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Summary: Not all the USB drivers were shown on task bar

  Steps to reproduce:
  Connect multiple(more than 2) usb keys to usb ports

  Expected result:
  USB keys will be shown on the task bar on the left side of screen.

  Actual result:
  Only 2 USB key icons were shown in the task bar, but we can see all the usb 
keys in folders view, at attached screenshot.

  Ubuntu Version: 20.04.1
  gnome-shell: 3.36.3-1ubuntu1~20.04.2
  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20200609-41+sutton-newell-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-10 (49 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200609-13:40
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 [modified: 
usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override 
usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js]
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  Tags: focal third-party-packages
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

[Rex Tsai]

Hi, Lukas and SRU taem

This one is blocking another SRU[1] for a certification platform.

If we would like land the #1887610 soon to meet the project schedule,
what would be the best approach to do this?

- Can we reduce the review time for this SRU, since it's verified?
- Or should we merge two SRU into one?

[1] https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887610

** Changed in: oem-priority
 Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1882161

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

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

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

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

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

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
 Assignee: (unassigned) => Shengyao Xue (xueshengyao)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1887610

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

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

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

[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

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

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1874567

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Invalid
Status in mutter source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Focal:
  New
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  
  When using the nouveau drivers, the orientation is applied correctly in gnome 
settings, and is persisted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

[Rex Tsai]

** Tags added: beaver-osp1-melisa

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1878670

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

Status in OEM Priority Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1882161

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  This bug originates from an OEM private bug #1875597, then ubuntu
  users reported 2 public bugs #1871329 and #1881659. The 2nd issue of
  #1871329 and the 1st issue of #1881659 have the same root cause as
  #1875597

  [Impact]
  On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.

  [Fix]
  The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.

  [Test Case]
  applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.

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

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window

[Rex Tsai]

** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1885673

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

Status in OEM Priority Project:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Step to reproduce:

  1. plug-in headset
  2. select headset in pop-up window.
  3. check g-c-c

  Expected result:
correct input is selected so that mic on the headset just works

  Actual result:
The correct input is not selected.

  a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

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

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

[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

[Rex Tsai]

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1881094

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     1. enable Pre-released updates in Developer Options
    Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-edge
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
 Assignee: (unassigned) => hugh chao (hugh712)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : 

[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

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

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

[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1881094

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  New

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
 1. enable Pre-released updates in Developer Options
Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-wip
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

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

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

[Desktop-packages] [Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting

[Rex Tsai]

** Changed in: oem-priority
 Assignee: Che Cheng (cktenn) => (unassigned)

** Changed in: oem-priority
   Importance: Low => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1844650

Title:
  No authentication window pops up if thunderbolt device be plugged
  before booting

Status in GNOME Shell:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  [Summary]
  In order to access the docking station resource, the system should pop up an 
authentication window after the cold boot. But, currently, no authentication 
window pops up after the cold boot. The authentication window only pops up 
after replugging it during the running state of the system.

  [Pre condition]
   - the testing thunderbolt device is not authenticated before
 - e.g. this is the 1st time you plugging this device.
 - e.g. execute `boltctl forget ${device}` to make sure target device not 
be authenticated

  [Steps to reproduce]
  1. keep the machine in the power-off state.
  2. Plugin the docking station(TB16/TB18)
  3. Boot up the system
  4. Check if an authentication window pops up after Ubuntu desktop displayed

  [Expected result]
  An authentication window pops up after Ubuntu desktop displayed

  [Actual result]
  No authentication window pops up after the cold boot

  [Failure rate]
  100%

  [Additional information]
  this issue can also be reproduced by  19.10 which has bolt 0.8-2 and kernel 
5.2.0-15-generic

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

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

[Desktop-packages] [Bug 1878670] Re: Gnome crash frequently

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Leon Liao (lihow731)

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1878670

Title:
  Gnome crash frequently

Status in OEM Priority Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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

[Desktop-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

[Rex Tsai]

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1872034

Title:
  [Focal] No HDMI output through thunderbolt docking station

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I can find monitor in display list, but no output from it.
  Also, I can't switch to extend mode, it failed to apply the setting and 
switched back to mirror mode.

  [Steps]
  1. Connect a thunderbolt docking station to thunderbolt port.
  2. Connect HDMI monitor to HDMI port on the docking station.
  3. Switch mode in display setting

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 16:44:40 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should disable gestures

[Rex Tsai]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/1774242

Title:
  Wacom touchscreens should disable gestures

Status in OEM Priority Project:
  In Progress
Status in xf86-input-wacom package in Ubuntu:
  Fix Released
Status in xf86-input-wacom source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  From the original bug:

  "The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either."

  [Test case]

  Install the update, note that the touchscreen behaviour is better.

  [Regression potential]

  From the upstream commit:

  "Note that this change will effectively cause a feature regression for
  users of other environments that do *not* have their own gesture
  engines (Cinnamon, KDE, MATE, XFCE, etc.). Users will want to add an
  xorg.conf.d snippet with `Option "Gesture" "on"` to bring back the
  functionality."

  but at least I (tjaalton) haven't heard of any complaints since we've
  disabled gestures in focal (Nov 21st), so the warning might be a bit
  too pessimistic about the impact.

  
  --

  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications 

[Desktop-packages] [Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting

[Rex Tsai]

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

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1844650

Title:
  No authentication window pops up if thunderbolt device be plugged
  before booting

Status in GNOME Shell:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  [Summary]
  In order to access the docking station resource, the system should pop up an 
authentication window after the cold boot. But, currently, no authentication 
window pops up after the cold boot. The authentication window only pops up 
after replugging it during the running state of the system.

  [Pre condition]
   - the testing thunderbolt device is not authenticated before
 - e.g. this is the 1st time you plugging this device.
 - e.g. execute `boltctl forget ${device}` to make sure target device not 
be authenticated

  [Steps to reproduce]
  1. keep the machine in the power-off state.
  2. Plugin the docking station(TB16/TB18)
  3. Boot up the system
  4. Check if an authentication window pops up after Ubuntu desktop displayed

  [Expected result]
  An authentication window pops up after Ubuntu desktop displayed

  [Actual result]
  No authentication window pops up after the cold boot

  [Failure rate]
  100%

  [Additional information]
  this issue can also be reproduced by  19.10 which has bolt 0.8-2 and kernel 
5.2.0-15-generic

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

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