[Desktop-packages] [Bug 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority/trusty Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in compiz package in Ubuntu: Confirmed Status in compiz-plugins-main package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1209400] Re: calculator fails to do proper calculations after CTRL+Z and Enter
*** This bug is a duplicate of bug 1209326 *** https://bugs.launchpad.net/bugs/1209326 ** Branch linked: lp:~lihow731/ubuntu/saucy/gnome-calculator/fix- for-1209326 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1209400 Title: calculator fails to do proper calculations after CTRL+Z and Enter Status in “gnome-calculator” package in Ubuntu: New Bug description: I found this bug trying to redo a calculation. Do a calculation maybe with decimals like I did and then press CTRL+Z and hit enter and you should see the bug. It's making a bad calculation after these steps. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-calculator 1:3.8.1-0ubuntu1 Uname: Linux 3.10.2-031002-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Aug 7 13:08:05 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-10 (28 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1209400/+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 1209326] Re: calculator fails to do proper calculatoins after CTRL+Z and Enter
** Branch linked: lp:~lihow731/ubuntu/saucy/gnome-calculator/fix- for-1209326 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1209326 Title: calculator fails to do proper calculatoins after CTRL+Z and Enter Status in GNOME Calculator: Confirmed Status in “gnome-calculator” package in Ubuntu: Triaged Status in “gnome-calculator” source package in Raring: Triaged Status in “gnome-calculator” source package in Saucy: Triaged Bug description: I found this bug trying to redo a calculation. Do a calculation maybe with decimals like I did and then press CTRL+Z and hit enter and you should see the bug. It's making a bad calculation after these steps. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-calculator 1:3.8.1-0ubuntu1 Uname: Linux 3.10.2-031002-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Aug 7 13:08:05 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-10 (28 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1209326/+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
** 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 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: Fix Released 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: Fix Released 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 · GitLab - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639 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 1903230] Re: Mutter release 3.36.7
@Timo, Could we wait for bug 1905825? -- 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/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Committed Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+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
** Merge proposal linked: https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/390544 ** Merge proposal unlinked: https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865 -- 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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Description changed: [Impact] - In some cases, the wow is not configured and the + 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 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 + 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. + 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 + 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. + * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network + won't management the WOW forever. [Other Info] - - * None + + * None ** 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. [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] * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network - won't management the WOW forever. + won't management the WOW function forever. The WOW function totally + depend on device driver. [Other Info] * None -- 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: Incomplete 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] * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network won't management the WOW function forever. The WOW function totally depend on device driver. [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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** 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 functiall still is normal. + 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] - * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network - won't management the WOW function forever. The WOW function totally - depend on device driver. + * This patch modifies the wake on lan parameters, please test that the + corresponding feature still works fine with the different configuration + values. [Other Info] * None -- 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: Incomplete 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. [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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Changed in: network-manager (Ubuntu Focal) Status: Incomplete => In Progress -- 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. [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 1891632] [NEW] The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
Public bug reported: 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. ** Affects: oem-priority Importance: Critical Assignee: Leon Liao (lihow731) Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Information type changed from Proprietary to Public ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Leon Liao (lihow731) ** Merge proposal linked: https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865 -- 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: 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. 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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Description changed: - In some cases, the wow is not configured and the + [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 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 -- 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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Also affects: oem-priority/focal Importance: Undecided Status: New ** No longer affects: oem-priority/focal -- 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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
The patch was merged into debian network-manager repository in https://salsa.debian.org/utopia-team/network-manager/-/commit/e7b44ef4c80907346ec7492a09c45277459924fc. For Groovy, when network-manager version >= 1.26.2, this patch will be included. For Focal, the network-manager (1.22.10) needs to carry on this patch. Append the debdiff for focal. ** Patch added: "network-manager_1.22.10-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891632/+attachment/5404329/+files/network-manager_1.22.10-1ubuntu2.2.debdiff -- 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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
Hi, I updated the description of the regression potential. Please check it. Thanks. ** 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 + 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 + * 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] * None ** Changed in: network-manager (Ubuntu Focal) Status: Incomplete => In Progress -- 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] * 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 1871563] [NEW] The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while.
Public bug reported: [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 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Affects: focal (Ubuntu) Importance: Undecided Status: New -- 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 chromium-browser package in Ubuntu: New 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+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 1871563] Re: The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while.
** Also affects: focal (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Leon Liao (lihow731) -- 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: New 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 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 1871563] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349383/+files/Lsusb-v.txt
--
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:
New
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 1871563] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349384/+files/ProcCpuinfo.txt
--
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:
New
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 1871563] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349380/+files/Lspci.txt
--
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:
New
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 1871563] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349379/+files/Dependencies.txt
--
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:
New
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 1871563] Re: The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while.
apport information
** Tags added: apport-collected focal snap
** Description changed:
[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.
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349378/+files/CurrentDmesg.txt
--
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:
New
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
[Desktop-packages] [Bug 1871563] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349381/+files/Lsusb.txt
--
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:
New
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 1871563] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349385/+files/ProcCpuinfoMinimal.txt
--
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:
New
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 1871563] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349386/+files/ProcEnviron.txt
--
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:
New
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 1871563] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349387/+files/ProcInterrupts.txt
--
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:
New
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 1871581] [NEW] The windw is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while
Public bug reported:
[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%
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 80.0.3987.163-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
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
Date: Wed Apr 8 16:44:47 2020
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 1.9T 6.5G 1.8T 1% /
tmpfs tmpfs 16G 193M 16G 2% /dev/shm
/dev/nvme0n1p2 ext4 1.9T 6.5G 1.8T 1% /
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
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic
root=UUID=a1145b98-763c-4de0-9ccf-5d3a6920bca7 ro quiet splash vt.handoff=7
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
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
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.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: Invalid
** Tags: amd64 apport-bug focal snap
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
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/1871581
Title:
The windw is frozen 3~10 seconds when swipe, pinch and zoom on the
google-map via touchscreen for a while
Status in chromium-browser package in Ubuntu:
Invalid
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%
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 80.0.3987.163-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
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
Date
[Desktop-packages] [Bug 1871563] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349382/+files/Lsusb-t.txt
--
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:
New
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 1871563] Snap.Info.core.txt
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349392/+files/Snap.Info.core.txt
--
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:
New
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 1871563] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349388/+files/ProcModules.txt
--
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:
New
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 1871563] Snap.Info.core18.txt
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349393/+files/Snap.Info.core18.txt
--
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:
New
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 1871563] Snap.Info.gtk-common-themes.txt
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349394/+files/Snap.Info.gtk-common-themes.txt
--
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:
New
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 1871563] Snap.Connections.txt
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349390/+files/Snap.Connections.txt
--
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:
New
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 1871563] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349395/+files/UdevDb.txt
--
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:
New
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 1871563] Snap.Info.chromium.txt
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349391/+files/Snap.Info.chromium.txt
--
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:
New
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 1871563] Snap.ChromiumPrefs.txt
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349389/+files/Snap.ChromiumPrefs.txt
--
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:
New
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 1772811] Re: [SRU] different behaviors for switch display mode between xenial and bionic
I verified this bug on bionic. After upgrade gnome-shell and mutter to 3.28.4-0ubuntu18.04.1, the video switch experience is better than original. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1772811 Title: [SRU] different behaviors for switch display mode between xenial and bionic Status in Mutter: Fix Released Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in mutter source package in Bionic: Fix Committed Status in gnome-shell source package in Disco: Fix Released Status in mutter source package in Disco: Fix Released Bug description: * Impact Need this SUR so that use OEM laptop hotkey won't be uesless. * Test case 1. Install the new mutter and gnome-shell on the target machine. 2. connect an external display. 3. Press either the monitor switch HOT key (each note book have different one), or the generic hot key (Meta-P) 4. Make sure the display mode is switch to next mode, not the first mode. * Regression potential very low, because it's merged upstream and also tested in oem platforms. -- When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1772811/+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 1835996] [NEW] Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel)
Public bug reported: [Summary] Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) [Reproduce Steps] 1. Install Ubuntu 16.04/18.04 on Precision 7730; 2. Disable automatic system sleep; 3. Wait for display to enter sleep; 4. Resume from display sleep. [Results] Expected: The screen wakes up as normal; Actual: The screen is flickering. [Additional Information] 1. This bug can be reproduced both Dell OEM Ubuntu 16.04 image and Canonical Ubuntu 16.04 image (Default video driver/firmware version is 390.25); 2. This bug still can be reproduced on Ubuntu 18.04; 3. "apt-get install nvidia current", the video driver/firmware version 304.135 will be installed. This bug does not appear with this driver; 4. Also tested version 331 (working properly) and version 384 (This bug can be reproduced.); 5. This bug does not appear on external monitors (working properly via WD15 and directly attached); 6 Same behavior with BIOS 1.4.2; 7. Similar behavior with RHEL Enterprise Linux Developer Workstation 7.5 64bit -> No video at all when attempting to resume from display sleep or system sleep; 8. System is working properly using Windows 10 Pro 64bit; 9. More information from customer: https://www.dell.com/community/XPS/Precision-7730-display-lined-flickering-in-BIOS-DO-NOT-BUY/td-p/6219020 ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- 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/1835996 Title: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) [Reproduce Steps] 1. Install Ubuntu 16.04/18.04 on Precision 7730; 2. Disable automatic system sleep; 3. Wait for display to enter sleep; 4. Resume from display sleep. [Results] Expected: The screen wakes up as normal; Actual: The screen is flickering. [Additional Information] 1. This bug can be reproduced both Dell OEM Ubuntu 16.04 image and Canonical Ubuntu 16.04 image (Default video driver/firmware version is 390.25); 2. This bug still can be reproduced on Ubuntu 18.04; 3. "apt-get install nvidia current", the video driver/firmware version 304.135 will be installed. This bug does not appear with this driver; 4. Also tested version 331 (working properly) and version 384 (This bug can be reproduced.); 5. This bug does not appear on external monitors (working properly via WD15 and directly attached); 6 Same behavior with BIOS 1.4.2; 7. Similar behavior with RHEL Enterprise Linux Developer Workstation 7.5 64bit -> No video at all when attempting to resume from display sleep or system sleep; 8. System is working properly using Windows 10 Pro 64bit; 9. More information from customer: https://www.dell.com/community/XPS/Precision-7730-display-lined-flickering-in-BIOS-DO-NOT-BUY/td-p/6219020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1835996/+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 1835996] Re: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel)
This bug only happened on AUO UHD#8CJK2 panel. Until now, we still don't know what is the root cause. Some information from nvidia: Add "option HardDPMS true" in xorg.conf, this bug won't be reproduced. But, only add this option, the screen will be frozen when we login (when the Enable Switchable graphic is enabled in BIOS settings.). Some information from ODM: Add below sections in xorg.conf, this bug won't be reproduced and we can login normally. Section "OutputClass" Identifier "nvidia" MatchDriver "nvidia-drm" Driver "nvidia" Option "AllowEmptyInitialConfiguration" ModulePath "/usr/lib/x86_64-linux-gnu/nvidia-418/xorg" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "Quadro P4200" Option "HardDPMS" "true" EndSection Section "Screen" Identifier "nvidia" Device "nvidia" Option "AllowEmptyInitialConfiguration" "Yes" EndSection Section "Device" Identifier "intel" Driver "modesetting" # Change BusID if necessary. Tips: (lspci | grep VGA) (Change 00:02.0 to 0:2:0) BusID "PCI:0:2:0" Option "AccelMethod" "none" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection -- 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/1835996 Title: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) [Reproduce Steps] 1. Install Ubuntu 16.04/18.04 on Precision 7730; 2. Disable automatic system sleep; 3. Wait for display to enter sleep; 4. Resume from display sleep. [Results] Expected: The screen wakes up as normal; Actual: The screen is flickering. [Additional Information] 1. This bug can be reproduced both Dell OEM Ubuntu 16.04 image and Canonical Ubuntu 16.04 image (Default video driver/firmware version is 390.25); 2. This bug still can be reproduced on Ubuntu 18.04; 3. "apt-get install nvidia current", the video driver/firmware version 304.135 will be installed. This bug does not appear with this driver; 4. Also tested version 331 (working properly) and version 384 (This bug can be reproduced.); 5. This bug does not appear on external monitors (working properly via WD15 and directly attached); 6 Same behavior with BIOS 1.4.2; 7. Similar behavior with RHEL Enterprise Linux Developer Workstation 7.5 64bit -> No video at all when attempting to resume from display sleep or system sleep; 8. System is working properly using Windows 10 Pro 64bit; 9. More information from customer: https://www.dell.com/community/XPS/Precision-7730-display-lined-flickering-in-BIOS-DO-NOT-BUY/td-p/6219020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1835996/+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 1836026] [NEW] There is no the screen rotation option in Settings with sensor LNG2DM
Public bug reported: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 ** Affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New ** Description changed: - If a machine has a g-sensor, the screen rotation option won't be drawn - in Settings. + If a machine has a accelerometer, the screen rotation option won't be + drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 -- 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/1836026 Title: There is no the screen rotation option in Settings with sensor LNG2DM Status in iio-sensor-proxy package in Ubuntu: New Bug description: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1836026/+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 1836026] Re: There is no the screen rotation option in Settings with sensor LNG2DM
If we add the hid-sensor-accel-3d module into blacklist, the screen rotation option will show up. -- 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/1836026 Title: There is no the screen rotation option in Settings with sensor LNG2DM Status in iio-sensor-proxy package in Ubuntu: New Bug description: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1836026/+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 1835996] Re: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel)
@Ho Cheung, Could you provide more information about the OS environment? For example the sosreport output that included ubuntu version, kernel version, amdgpu version ...) -- 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/1835996 Title: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) [Reproduce Steps] 1. Install Ubuntu 16.04/18.04 on Precision 7730; 2. Disable automatic system sleep; 3. Wait for display to enter sleep; 4. Resume from display sleep. [Results] Expected: The screen wakes up as normal; Actual: The screen is flickering. [Additional Information] 1. This bug can be reproduced both Dell OEM Ubuntu 16.04 image and Canonical Ubuntu 16.04 image (Default video driver/firmware version is 390.25); 2. This bug still can be reproduced on Ubuntu 18.04; 3. "apt-get install nvidia current", the video driver/firmware version 304.135 will be installed. This bug does not appear with this driver; 4. Also tested version 331 (working properly) and version 384 (This bug can be reproduced.); 5. This bug does not appear on external monitors (working properly via WD15 and directly attached); 6 Same behavior with BIOS 1.4.2; 7. Similar behavior with RHEL Enterprise Linux Developer Workstation 7.5 64bit -> No video at all when attempting to resume from display sleep or system sleep; 8. System is working properly using Windows 10 Pro 64bit; 9. More information from customer: https://www.dell.com/community/XPS/Precision-7730-display-lined-flickering-in-BIOS-DO-NOT-BUY/td-p/6219020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1835996/+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 1835996] Re: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel)
Update some information: On Precision 7730 with NVIDIA GPU, this bug is fixed in graphic driver nvidia 430.40. When you installed nvidia 430.40 via .run file that downloaded from NVIDIA official website, there is no any side effect. If you installed nvidia 430.44 via .deb or apt (for example: https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa), there is a side effect: If the nvidia graphic VID:PID are 10de:1bb5, 10de:1bb9 and 10de:1bbb, the gdm could not be started well. Fortunate, there is a workaround that mark or remove below line in /lib/udev/rules.d/71-nvidia.rules. ACTION=="add" DEVPATH=="/module/nvidia" SUBSYSTEM=="module" RUN+="/usr/bin/nvidia-smi" -- 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/1835996 Title: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel) [Reproduce Steps] 1. Install Ubuntu 16.04/18.04 on Precision 7730; 2. Disable automatic system sleep; 3. Wait for display to enter sleep; 4. Resume from display sleep. [Results] Expected: The screen wakes up as normal; Actual: The screen is flickering. [Additional Information] 1. This bug can be reproduced both Dell OEM Ubuntu 16.04 image and Canonical Ubuntu 16.04 image (Default video driver/firmware version is 390.25); 2. This bug still can be reproduced on Ubuntu 18.04; 3. "apt-get install nvidia current", the video driver/firmware version 304.135 will be installed. This bug does not appear with this driver; 4. Also tested version 331 (working properly) and version 384 (This bug can be reproduced.); 5. This bug does not appear on external monitors (working properly via WD15 and directly attached); 6 Same behavior with BIOS 1.4.2; 7. Similar behavior with RHEL Enterprise Linux Developer Workstation 7.5 64bit -> No video at all when attempting to resume from display sleep or system sleep; 8. System is working properly using Windows 10 Pro 64bit; 9. More information from customer: https://www.dell.com/community/XPS/Precision-7730-display-lined-flickering-in-BIOS-DO-NOT-BUY/td-p/6219020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1835996/+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] [NEW] The cancel button of the paring dialog does not work during paring a bluetooth keyboard
Public bug reported: The cancel button of the paring dialog does not work during paring 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 paring XXX dialog show up 3. click the Cancel button (on the top left of the dialog). Expected: the Cancel button is work. And, the paring is canceled normally. Actually: the Cancel button does not work. The paring action can not be canceled via the button. Ubuntu: 18.04 gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Description changed: The cancel button of the paring dialog does not work during paring a bluetooth keyboard. The dialog can be cancel via press the "ESC" on the keyboard. - But, after around 1 minute, the gnome-control-center is crashed. - + 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 paring XXX dialog show up 3. click the Cancel button (on the top left of the dialog). Expected: the Cancel button is work. And, the paring is canceled normally. Actually: the Cancel button does not work. The paring action can not be canceled via the button. - Ubuntu: 18.04 gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3 -- 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 paring a bluetooth keyboard Status in gnome-control-center package in Ubuntu: New Bug description: The cancel button of the paring dialog does not work during paring 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 paring XXX dialog show up 3. click the Cancel button (on the top left of the dialog). Expected: the Cancel button is work. And, the paring is canceled normally. Actually: the Cancel button does not work. The paring 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/ubuntu/+source/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 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard
** Summary changed: - The cancel button of the paring dialog does not work during paring a bluetooth keyboard + The cancel button of the paring dialog does not work during pairing a bluetooth keyboard ** Description changed: - The cancel button of the paring dialog does not work during paring a bluetooth keyboard. + 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 paring XXX dialog show up + 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 paring is canceled normally. - Actually: the Cancel button does not work. The paring action can not be canceled via the button. + 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 ** 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-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 OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New 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/oem-priority/+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 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)
There is a workaround solution to avoid this bug. It is to disable the amdgpu runtime suspend. Just add amdgpu.runpm=0 on the kernel command line. ** 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 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 1847219] [NEW] HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)
Public bug reported: 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 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- 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 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)
There is a workaround solution to avoid this bug. It is to disable the amdgpu runtime suspend. Just add amdpug.runpm=0 on the kernel command line. -- 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 1774242] Re: Wacom touchscreens should use libinput, not wacom driver
@Timo, I verified the method to add the option "Option Gesture Off" without uncomment the touchscreen class(es) on new Dell XPS 13. This method works. The config is here: https://bugs.launchpad.net/somerville/+bug/1840605/comments/7 -- 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 use libinput, not wacom driver Status in xf86-input-wacom package in Ubuntu: Fix Released Bug description: /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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+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 1716359] Re: Unplugging headset with audio panel open mutes internal mic
@Brian, This is from OEM team. We had verified the unity-control-center 15.04.0+16.04.20170214-0ubuntu2. This bug can not be reproduced with the unity-control-center on -proposed. -- 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/1716359 Title: Unplugging headset with audio panel open mutes internal mic Status in OEM Priority Project: Fix Committed Status in unity-control-center package in Ubuntu: Invalid Status in unity-control-center source package in Xenial: Incomplete Bug description: Impact == This is required by OEM team. Test Case = 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status Make sure the internal mic is not muted. Regression Potential === - Make sure that plugging/unplugging headphones does the correct thing. - Make sure that manually selecting an headphone actually switch mic. - Please also check that output sound works too. Original Bug Report === This bug was reported by our OEM team, I'm opening this public bug. The internal microphone is muted after he headset is unplugged when the System Settings is running. We can not reproduce this bug when closed the System Settings window before unplugged the headset. Reproduce steps: 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1716359/+subscriptions -- Mailing list: https://launchpad.net/~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 1716359] Re: Unplugging headset with audio panel open mutes internal mic
@Chris, I verified below check items on DELL Latitude 7490: - Verifying that plugging/unplugging headphones does the correct thing: Pass When plugging a headphone, the Unknow Audio Device dialog will pop up. And, the headphone works fine. When unplugging the headphone, the device will be remove from the Settings list. When plugging a headset, Unknow Audio Device dialog will pop up. And, Both input and output function works fine. When unplugging the headset, the device will be remove from the Settings list. When plugging a microphone, Unknow Audio Device dialog will pop up. And, the microphone works fine. When unplugging the microphone, the device will be remove from the Settings list. - Verifying that manually selecting a headphone actually switches the mic: Pass When plugging a headphone and switching the input device manually, only Internal Microphone works. The "Headset Microphone" and "Microphone" do not work. When plugging a headset and switching the input device manually, the "Internal Microphone" and "Headset Microphone" work. The "Microphone" does not work. When plugging a microphone and switching the input device manually, the "Internal Microphone" and "Microphone" work. The "Headset Microphone" does not work. - Checking that output sound works too: Pass When plugging a headphone and switching the output device manually, both the "Speakers" and "Headphones" work. When plugging a headset and switching the output device manually, both the "Speakers" and "Headphones" work. When plugging a microphone and switching the output device manually, only the "Speakers" works. The "Headphones" does not work. -- 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/1716359 Title: Unplugging headset with audio panel open mutes internal mic Status in OEM Priority Project: Fix Committed Status in unity-control-center package in Ubuntu: Invalid Status in unity-control-center source package in Xenial: Incomplete Bug description: Impact == This is required by OEM team. Test Case = 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status Make sure the internal mic is not muted. Regression Potential === - Make sure that plugging/unplugging headphones does the correct thing. - Make sure that manually selecting an headphone actually switch mic. - Please also check that output sound works too. Original Bug Report === This bug was reported by our OEM team, I'm opening this public bug. The internal microphone is muted after he headset is unplugged when the System Settings is running. We can not reproduce this bug when closed the System Settings window before unplugged the headset. Reproduce steps: 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1716359/+subscriptions -- Mailing list: https://launchpad.net/~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 1716359] Re: Unplugging headset with audio panel open mutes internal mic
@Brian and @Chris, The "Regression Potential" items have been verified. Could this unity-control-center in -proposed be SRU? -- 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/1716359 Title: Unplugging headset with audio panel open mutes internal mic Status in OEM Priority Project: Fix Committed Status in unity-control-center package in Ubuntu: Invalid Status in unity-control-center source package in Xenial: Incomplete Bug description: Impact == This is required by OEM team. Test Case = 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status Make sure the internal mic is not muted. Regression Potential === - Make sure that plugging/unplugging headphones does the correct thing. - Make sure that manually selecting an headphone actually switch mic. - Please also check that output sound works too. Original Bug Report === This bug was reported by our OEM team, I'm opening this public bug. The internal microphone is muted after he headset is unplugged when the System Settings is running. We can not reproduce this bug when closed the System Settings window before unplugged the headset. Reproduce steps: 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1716359/+subscriptions -- Mailing list: https://launchpad.net/~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 1772811] [NEW] Can not select Video mode precisely by Video-out hotkey
Public bug reported: When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1772811 Title: Can not select Video mode precisely by Video-out hotkey Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+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 1772811] Re: Can not select Video mode precisely by Video-out hotkey
** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772811 Title: Can not select Video mode precisely by Video-out hotkey Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+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 1772811] Re: Can not select Video mode precisely by Video-out hotkey
The attached is the video when we press down the video-out key. ** Attachment added: "IMG_3993.MOV" https://bugs.launchpad.net/oem-priority/+bug/1772811/+attachment/5143166/+files/IMG_3993.MOV -- 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/1772811 Title: Can not select Video mode precisely by Video-out hotkey Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+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 1772831] [NEW] gnome-control-center does not respond after we set the resolution 320x180
Public bug reported: gnome-control-center does not respond after we set the resolution 320x180 Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! Notebook: Dell XPS 13 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center does not respond after we set the resolution 320x180 Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! Notebook: Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772831/+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 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
The attached movie shows how to reproduce this bug. ** Attachment added: "IMG_3995.MOV" https://bugs.launchpad.net/oem-priority/+bug/1772831/+attachment/5143244/+files/IMG_3995.MOV -- 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/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center does not respond after we set the resolution 320x180 Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! Notebook: Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772831/+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 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
@Will, The OS works well in the resolution 800x600. @Sebastien, The attached file is the output of "journalctl". ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772831/+attachment/5143696/+files/journalctl.log -- 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/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center does not respond after we set the resolution 320x180 Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! Notebook: Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772831/+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 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
I installed the gnome-session and select the gdm3. At first, The resolution can be set to 320x180, the countdown dialog show up. But, I fail to set the resolution to 320x180 at second time. The error message looks different. The attached file is the output of journalctl with gnome-session. ** Attachment added: "journal-gnome-session.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772831/+attachment/5143736/+files/journal-gnome-session.log -- 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/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center does not respond after we set the resolution 320x180 Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! Notebook: Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772831/+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 1789913] Re: X crashes with "randr: falling back to unsynchronized pixmap sharing" when connecting to an external monitor via HDMI (I+A)
I verified the xserver-xorg-core-hwe-16.04 on Dell Precision 7730(I+A). This external monitor works normal. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1789913 Title: X crashes with "randr: falling back to unsynchronized pixmap sharing" when connecting to an external monitor via HDMI (I+A) Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server source package in Xenial: Won't Fix Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xorg-server source package in Bionic: Fix Committed Status in xorg-server-hwe-16.04 source package in Bionic: Invalid Bug description: [Impact] X server crashes in certain cases on I+A hybrid machines with modesetting+amdgpu drivers. [Test case] Connect an external monitor, check that it doesn't crash X. [Regression potential] This commit was provided by AMD and reviewed by an NVIDIA engineer, and after a few iterations it got applied upstream. We'll test it with many driver combinations (modesetting+amdgpu, m+nvidia, m+m...) to check that they all (still) work. -- Copied from a private bug: - Steps to see the issue: 1. Connect a monitor to UUT via HDMI port Expected Result: Video outputs successfully in the monitor Actual Result: X crashes into a login screen - BIOS: 0.7.3 - AMD driver release: 18.10, 18.20RC8 and 18.20RC9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789913/+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
On 16.04, could anyone test this solution? $ sudo add-apt-repository ppa:lihow731/xenial $ sudo apt-get update $ sudo apt-get install oem-workaround-touchpad-block-synps2 Then, re-login Xserver. For more detail: https://ubuntuforums.org/showthread.php?t=2316240&p=13461233#post13461233 -- 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 1351772] Re: "disable touchpad while typing" doesn't work
@Christopher and Tessa, Yes. you can install it in 16.10 and 17.04 using the same commands in comment 16. This package will install a configure file into /usr/share/X11/xorg.conf.d/. This configure will block the "SynPS/2 Synaptics Touchpad" (You could check it via "xinput" command). If your touchpad is a I2C touchpad and the "SynPS/2 Synaptics Touchpad" exists, this package should work for you. -- 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 1351772] Re: "disable touchpad while typing" doesn't work
@Christopher, Could you upload the output of the "xinput" of your machine (Thinkpad T450s)? We are still debugging why the "disable tap while typing" lost function when both the i2c and ps/2 devices exist. For the track pad case, we don't have solution yet. -- 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 1351772] Re: "disable touchpad while typing" doesn't work
@Christopher, On Thinkpad T450s, there is only one trackpad device in xinput, and it's a PS/2 device. So, Thinkpad T450s does not need this workaround solution. The workaround solution is to block the PS/2 trackpad device. That's why the workaround solution make your trackpad lost function. I think I need add more condition in the workaround package. I borrowed a thinkpad X250, the xinput is similar with yours beside the Wacom Bamboo 2FG and the touchscreen. When I am typing, the 'tap to click' is disabled. So, I won't be interrupt by palm when I typing. For your case, I have no idea what causes the "disable tap while typing" function fail. Another thing, the "disable touchpad while typing" option is removed. Currently, the actual behavior is "disable 'tap to click' while typing". I think this behavior make sense, i.e. Some gamers will use both the keyboard and the touchpad at the same time. -- 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 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
I verified the mutter=3.28.3-2~ubuntu18.04.1 on Dell Inspiron 5480. The resolutions is keeped larger than 800x512. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 Status in gnome-control-center: Fix Released Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] gnome-control-center does not respond after we set the resolution 320x180 [ Test case ] Open gnome-control-center -> Displays Low resolutions (such as 320x180) should not be listed. Trying to set the lowst listed resolution, should just apply without breaking gnome-control-center. [ Regression potential ] No alternative resolutions are shown in g-c-c --- Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! Notebook: Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+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 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
** Changed in: oem-priority Status: Confirmed => Fix Committed -- 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/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 Status in gnome-control-center: Fix Released Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] gnome-control-center does not respond after we set the resolution 320x180 [ Test case ] Open gnome-control-center -> Displays Low resolutions (such as 320x180) should not be listed. Trying to set the lowst listed resolution, should just apply without breaking gnome-control-center. [ Regression potential ] No alternative resolutions are shown in g-c-c --- Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! Notebook: Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+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 1716359] Re: Unplugging headset with audio panel open mutes internal mic
I can not reproduce this bug with the unity-control-center 15.04.0+16.04.20170214-0ubuntu2 on DELL Latitude 7490. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1716359 Title: Unplugging headset with audio panel open mutes internal mic Status in OEM Priority Project: Confirmed Status in unity-control-center package in Ubuntu: Invalid Status in unity-control-center source package in Xenial: Fix Committed Bug description: Impact == This is required by OEM team. Test Case = 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status Make sure the internal mic is not muted. Regression Potential === - Make sure that plugging/unplugging headphones does the correct thing. - Make sure that manually selecting an headphone actually switch mic. - Please also check that output sound works too. Original Bug Report === This bug was reported by our OEM team, I'm opening this public bug. The internal microphone is muted after he headset is unplugged when the System Settings is running. We can not reproduce this bug when closed the System Settings window before unplugged the headset. Reproduce steps: 1. Open System Settings -> Sound -> select the input tab 2. Plug headset and select Headset on Unknown Audio Device dialog. 3. Check external mic is working 4. Adjust the internal microphone volume.(Just change the volume value.) 5. Adjust headset input volume around 100% in Input tab from Sound settings 6. Unplug headset 7. Check internet mic status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1716359/+subscriptions -- Mailing list: https://launchpad.net/~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
The attached file is the xinput output of XPS13. ** Attachment added: "xinput.list" https://bugs.launchpad.net/oem-priority/+bug/1672619/+attachment/4903908/+files/xinput.list -- 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: Confirmed Status in xserver-xorg-input-synaptics package in Ubuntu: New 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
