[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
They are used for different platform of different OEM. The OEM platform owner tracks specific platform bugs by platform tag in the private bug and we are not able to share the platform information cross OEM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936703] Re: screen keyboard doesn't work on authentication window
** Tags added: 2-in-1 apport-collected jammy oem-priority wayland- session ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1936703 Title: screen keyboard doesn't work on authentication window Status in GNOME Shell: New Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Before reporting the bug, lets me mention my hate about you, abandoned 'onboard'. Bug description: pressing key on screen keyboard doesn't work on authentication window, until you press [Enter]. See screenshot ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 17 04:41:09 2021 EcryptfsInUse: Yes InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/ubuntu.seed quiet splash --- InstallationDate: Installed on 2021-06-17 (29 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936703/+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 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
** Changed in: oem-priority Status: New => Fix Committed -- 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/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: Fix Committed Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
I believe the fix for u-d-c is landed in jammy-updates for a long?
commit b44aeb56032d14aef4a46dab5411875ca8868e3f
Author: Alberto Milone
Date: Tue Aug 2 16:16:50 2022 +0200
UbuntuDrivers/detect.py: make sure -open drivers have a lower
priority
diff --git a/UbuntuDrivers/detect.py b/UbuntuDrivers/detect.py
index 25d32ee..439e97f 100644
--- a/UbuntuDrivers/detect.py
+++ b/UbuntuDrivers/detect.py
@@ -1096,10 +1096,17 @@ def _pkg_support_from_cache(x):
def _cmp_gfx_alternatives(x, y):
'''Compare two graphics driver names in terms of preference. (desktop)
+-open always sorts after non-open.
-server always sorts after non-server.
LTSB (Long Term Support Branch) always sorts before NFB (New Feature
Branch).
Legacy always sorts before Beta.
'''
+
+if x.endswith('-open') and not y.endswith('-open'):
+return -1
+if not x.endswith('-open') and y.endswith('-open'):
+return 1
+
if x.endswith('-server') and not y.endswith('-server'):
return -1
if not x.endswith('-server') and y.endswith('-server'):
--
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/1988836
Title:
LRMv7: Enable the open NVIDIA kernel modules
Status in linux-restricted-modules package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in linux-restricted-modules source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
Fix Released
Status in ubuntu-drivers-common source package in Focal:
Fix Committed
Status in linux-restricted-modules source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Fix Committed
Bug description:
[ Impact ]
* The 515 series introduced open kernel modules for the NVIDIA driver. They
come with an open source licence, and should be provided as an option for
datacenter GPUs:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
Currently, this is only production-ready (and enabled) on
datacenter GPUs.
* We should enable signed modules for the 515-open drivers, giving
users the option to try the drivers.
* The ubuntu-drivers tool should set a lower priority for the -open
flavour, so that we do not end up recommending it over the plain 515
flavour.
[ Test Plan ]
* [ubuntu-drivers-common]:
"sudo ubuntu-drivers install (to make sure the driver is not installed by
default)"
* [nvidia driver]
"sudo ubuntu-drivers install nvidia:515-open" to make sure that the
driver can be installed manually.
Please make sure that this installs the correct linux-restricted-
modules.
Note: support for GeForce and Workstation GPUs is alpha-quality,
and is disabled by default. This means that desktop testing is not
needed at the moment.
[ Where problems could occur ]
* This adds a new driver combination, which is not meant to be default, and
is only enabled for a limited amount of devices (datacenter GPUs).
* We need to be sure that the driver is not recommended over the other
drivers.
[ Other Info ]
-
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Changed in: oem-priority
Status: Triaged => Fix Released
--
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/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Fix Released
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2003169 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
okay, I can confirmed it works with latest packages from Jammy. In both 'Launch using Discrete Graphics Card' and '__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia' cases. But it doesn't work for firefox (mine is a snap version) so I think we are good to close this or switch to affect firefox. ** Changed in: oem-priority Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Invalid Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
The original schedule of this feature hopes could be in last year.
Unfortunately, I've no time to cook this in previous months.
This ticket should be converted to a SRU ticket now.
Sorry for the noise.
** Summary changed:
- [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
+ [Draft][SRU] Support to install nvidia driver by allowing list
** Changed in: oem-priority
Status: Incomplete => Confirmed
--
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/1990341
Title:
[Draft][SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Incomplete
Bug description:
> If the upload is a new upstream microrelease, the relevant part of
the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for
more details.
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows
"DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when
enables the verbose.
2. try non exist nv driver (e.g. 525, ha
[Desktop-packages] [Bug 1990341] Re: [Draft][SRU] Support to install nvidia driver by allowing list
** Description changed:
- > If the upload is a new upstream microrelease, the relevant part of the
- upstream changelog and/or release notes
+ [ Impact ]
- Upstream commit: https://github.com/tseliot/ubuntu-drivers-
- common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
+ * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
+ OEM/ODM for production.
- > An explanation of the testing which has been performed on the new
- version in Ubuntu, including verification that the new package:
+ In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to
+ use a specific nvidia version to development/production.
- For this feature which only impact if the target system has a custom
+ NVIDIA and OEN/ODM will announce the next generation combination at the
+ same time usually when the factory ready to ship the product.
+
+ We made Ubuntu as a leading distribution supports many cutting edge
+ devices, it's time to have an official way to make the nvidia
+ installation consistent in unannounced (yet) nvidia devices to support
+ OEM/ODM factory shipment for our growing counterparts.
+
+ [ Test Plan ]
+
+ * For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
- * different version type: 390/470/495/510..
+ * different version type: 390/470/495/510/520/525..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
- 1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
+ 1. Normal case (Stock ubuntu), without /etc/custom_supported_gpus.json in the
system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more
details.
- > state the reason why you feel it is necessary (other bugs it fixes,
- etc.)
-
- related bug: https://bugs.launchpad.net/ubuntu/+bug/1
-
- In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
- In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
-
- NVIDIA and OEN/ODM will announce the next generation combination at the
- same time usually when the factory ready to ship the product.
-
- We made Ubuntu as a leading distribution supports many cutting edge
- devices, it's time to have an official way to make the nvidia
- installation consistent in unannounced (yet) nvidia devices to support
- OEM/ODM factory shipment for our growing counterparts.
-
- > attach (as files)
- > diff of the Upstream ChangeLog (not debian/changelog)
- > diff -u -{old-version,new-version}/ChangeLog > changelog.diff
- note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
- > the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
-
- N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
-
- > build log (as file)
-
- Please refer the attachment "buildlog"
-
- > install log
-
- Please refer the attachment "installlog"
-
- > mention what testing you've done to see that it works
+ * Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
- ```
- P.S. also tried:
- 1. wrong j
[Desktop-packages] [Bug 2009767] Re: external HDMI monitor is laggy on NV reverse PRIME system
** Tags added: originate-from-2003066 stella -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: external HDMI monitor is laggy on NV reverse PRIME system Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: New Bug description: [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be blak in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009767] Re: external HDMI monitor is laggy on NV reverse PRIME system
** Tags added: originate-from-2009792 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: external HDMI monitor is laggy on NV reverse PRIME system Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: New Bug description: [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be blak in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009767] Re: external HDMI monitor is laggy on NV reverse PRIME system
Hi Daniel, The fix for this issue not only requires xorg 1.21.1.4, but also a newer version of the Nvidia driver. We have confirmed that the combination that fixes this issue is (1) xorg 1.21.1.4 (from Kinetic) + (2) a development version of the Nvidia driver, which is under NDA. To be honest, Nvidia is also a black box for us. We don't know the root cause of the lag or whether it affects only the Nvidia-525. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: external HDMI monitor is laggy on NV reverse PRIME system Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Confirmed Bug description: [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be blak in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009767] Re: external HDMI monitor is laggy on NV reverse PRIME system
Yes, a nvidia tracker is needed. There are some questions we need to sync with nvidia. The Xorg task is needed (for jammy) because the nvidia driver will check the version of Xorg (need 1.21.1.4+) to turn-on some features. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: external HDMI monitor is laggy on NV reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be blak in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
** 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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time Status in OEM Priority Project: Fix Released Status in gdm3 package in Ubuntu: Fix Released Bug description: [Steps to reproduce] 1. Install Jammy daily build 2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037 3. reboot with no attach monitor 4. attach monitor after booting [Expect result] external monitor works directly [Actual result] system go back to gdm login screen [Additional information] 1. the external port is connecting to dGPU. 2. happens on wayland only 3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 21:22:47 2022 InstallationDate: Installed on 2022-04-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Tags added: nvidia-wayland -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.
[Desktop-packages] [Bug 1942791] Re: _has_integrated_gpu() needs to consider the desktop case
as #2. ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: nvidia-prime (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942791 Title: _has_integrated_gpu() needs to consider the desktop case Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Bug description: In recovery (from a storage) case, the /var/lib/ubuntu-drivers- common/last_gfx_boot is empty. Thus, the _has_integrated_gpu() returns false in I+N laptop case. In this case, there is a iGPU actually. --- During the recovery, a worker executes ubuntu-drivers install. The expected result is "on-demand" but it goes to "on" because /var/lib/ubuntu-drivers-common/last_gfx_boot doesn't exist `ubuntu-drivers install` calls `prime-select on-demand` calls enable_profile() and then enable_profile() calls _has_integrated_gpu() before switching mode. Since _has_integrated_gpu() returns false, it won't switch nvidia mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Tags added: originate-from-1982919 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Confirmed Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 2000459] [NEW] Only shows half of menu if right-clicks mouse on the desktop if scaling screen
Public bug reported: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% ** Affects: oem-priority Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1993786 sutton -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+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 2000459] Re: Only half of menu if right-clicks mouse on the desktop if scaling screen
** Attachment added: "issue video.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000459/+attachment/5637716/+files/issue%20video.mp4 -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+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 2000459] Re: Only half of menu if right-clicks mouse on the desktop if scaling screen
** Attachment added: "menu.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000459/+attachment/5637717/+files/menu.jpg -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+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 2000459] Re: Only half of menu if right-clicks mouse on the desktop if scaling screen
** Attachment added: "sosreport-u-ThinkStation-P360-Tower-2022-10-24-cldksuc.tar.xz" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000459/+attachment/5637719/+files/sosreport-u-ThinkStation-P360-Tower-2022-10-24-cldksuc.tar.xz ** Tags added: oem-priority originate-from-1993786 sutton ** Summary changed: - Only half of menu if right-clicks mouse on the desktop if scaling screen + Only shows half of menu if right-clicks mouse on the desktop if scaling screen -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+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 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
** Changed in: oem-priority
Status: Confirmed => In Progress
--
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/1990341
Title:
[FeatureFreeze Exceptions] Support to install nvidia driver by
allowing list
Status in OEM Priority Project:
In Progress
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
> If the upload is a new upstream microrelease, the relevant part of
the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
TBC, I'll provide soon.
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
build log
** Description changed:
> If the upload is a new upstream microrelease, the relevant part of the
upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the
same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
- TBC, I'll provide soon.
+ As the attachment "buildlog"
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
** Attachment added: "buildlog"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5638891/+files/buildlog_ubuntu-jammy-amd64.ubuntu-drivers-common_1%200.9.6.2~0.22.04.1+lp1990341_BUILDING.txt.gz
--
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/1990341
Title:
[FeatureFreeze Exceptions] Support to install nvidia driver by
allowing list
Status in OEM Priority Project:
In Progress
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
> If the upload is a new upstream microrelease, the relevant part of
the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
As the attachment "buildlog"
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
** Description changed:
> If the upload is a new upstream microrelease, the relevant part of the
upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
- I will build a version soon. TBC
+ For this feature which only impact if the target system has a custom
+ file "/etc/custom_supported_gpus.json"
+
+ If the file presents, it will effect packages_for_modalias() and
+ _is_runtimepm_supported(). Both functions are important when "ubuntu-
+ driver install" a nvidia driver.
+
+ For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
+ * different branch type: LTS/PB/NFB/Legacy..
+ * different version type: 390/470/495/510..
+ * For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
+ which contains:
+ 1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
+ 2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
+ 3. /etc/custom_supported_gpus.json point to the older version than candidate.
+ 4. /etc/custom_supported_gpus.json point to the same version than candidate.
+ 5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
+
+ and you can see from "buildlog" attachment, all passed as well as
+ "test_system_driver_packages_force_install_nvidia()"
+
+ Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more
+ details.
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the
same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
- As the attachment "buildlog"
+ Please refer the attachment "buildlog"
> install log
- TBC, I'll provide soon.
+ Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
** Attachment added: "installlog"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5638895/+files/installlog
--
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/1990341
Title:
[FeatureFreeze Exceptions] Support to install nvidia driver by
allowing list
Status in OEM Priority Project:
In Progress
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
> If the upload is a new upstream microrelease, the relevant part of
the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/
[Desktop-packages] [Bug 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
** Description changed:
> If the upload is a new upstream microrelease, the relevant part of the
upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more
details.
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the
same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
+
+ ---
+
+ [Additional information]
+ * Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
** Description changed:
> If the upload is a new upstream microrelease, the relevant part of the
upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force
[Desktop-packages] [Bug 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
** Description changed:
> If the upload is a new upstream microrelease, the relevant part of the
upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more
details.
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the
same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
- TBC, I'll provide soon.
+ 1. pick a cutting edge nvidia graphic.
+ 2. remove nv-525 from the pool.
+ 3. add ppa, apt update and reboot.
+ 4. check the nv support status:
+ ```
+ $ ubuntu-drivers list
+ oem-fix-gfx-nvidia-ondemandmode
+ libfprint-2-tod1-broadcom
+ oem-somerville-cinccino-meta
+ ```
+ 5. modify custom file
+ ```
+ $ cat /etc/custom_supported_gpus.json
+ {
+ "chips": [
+ {
+ "devid": "0x24BA",
+ "name": "TEST 24BA",
+ "branch": "580.1234",
+ "features": [
+ "runtimepm"
+ ]
+ },
+ {
+ "devid": "0x25BC",
+ "name": "TEST 25BC",
+ "branch": "510",
+ "features": [
+ "runtimepm"
+ ]
+ }
+ ]
+ }
+ ```
+ 6. make sure the hook works
+ ```
+ $ ubuntu-drivers list
+ nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
+ oem-fix-gfx-nvidia-ondemandmode
+ libfprint-2-tod1-broadcom
+ oem-somerville-cinccino-meta
+ ```
+
+ P.S. also tried:
+ 1. wrong json format and it shows
"DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when
enables the verbose.
+ 2. try non exist nv driver (e.g. 525, has been remove from the pool) and it
shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
+
+ The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341
** Description changed:
> If the upload is a new upstream microrelease, the relevant part of the
upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute
Hi, I aware the adobe is not longer support since this year. but the postinst[1] is still trying to get something from remote server. as ``` upstream=$(HOME=/root wget -q -O- "https://get.adobe.com/flashplayer/webservices/json/?platform_type=Linux&platform_arch=$arch&browser_dist=Chrome";...) ``` and it will take 4 hours to wait for the response. --- 16:17:01 Setting up pepperflashplugin-nonfree (1.8.3+nmu1ubuntu1) ... 20:11:51 ERROR: failed to determine upstream version 20:11:51 More information might be available at: 20:11:51 http://wiki.debian.org/PepperFlashPlayer --- As comment#7, please consider to backport to bionic as well. [1] ``` update-pepperflashplugin-nonfree --install --fast || true ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in OEM Priority Project: New Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+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 1871471] Re: flash end of life soon, suggest remove from hirsute
** Tags added: oem-priority originate-from-1910660 timbuktu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in OEM Priority Project: New Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+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 1871471] Re: flash end of life soon, suggest remove from hirsute
** Tags added: bionic ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Importance: Critical => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in OEM Priority Project: Triaged Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I'd confirmed the regression with enabling Wayland. Due to nvidia-driver (nvidia-driver-440) disable wayland as default, I'll separate the verification to two scenarios. 1. Make sure the new gdm3 fixes this issue. 2. Make sure the new gdm3 without the regression (https://gitlab.gnome.org/GNOME/gdm/-/issues/602) --- * Make sure the new gdm3 fixes this issue * [Summary] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1. Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically". 2. Install with default options 2.1 Install nvidia-driver-440 (450.66-0ubuntu2) from ubuntu-archive. 2.2 Enable "Login automatically" from system settings. After reboot, the system won't login automatically even can not login manually. [Environment] HP 800 G6 DM + GeForce GTX 1660 [10de:2191] [Solution] Backport the solution from comment#119 as a debian package[2] (commit ID from upstream: f843233a, 690b3c01). The problem is solved. (Verified in scenario 2) The debdiff as attachment, please help to review. [1] sha256sum ``` $ sha256sum ~/Downloads/groovy-desktop-amd64.iso bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 /home/jeremysu/Downloads/groovy-desktop-amd64.iso ``` [2] gdm3 from https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801/+packages --- * Make sure the new gdm3 without the regression (https://gitlab.gnome.org/GNOME/gdm/-/issues/602) * This issue is happens when switching user under Wayland. I'd verified gdm3#602 issue when using intel graphic in the same machine because nvidia-driver disable Wayland as default. Steps to reproduce gdm3#602 issue: 1. Login a user "test" under x11 2. Create a user "test2" 3. Press "switch user ..." to "test2" under wayland 4. Switch back to "test" under x11 5. Switch to "test2" under wayland (then the running session be killed immediately) 6. Login again and then the mouse won't work. After applying commit 690b3c01, above problems are solved. Repeat to switch user and everything goes well. ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5406013/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Description changed: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: - 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. + 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 - [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 - [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 + [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 + [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKern
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407602/+files/gdm3_3.34.1-1ubuntu2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: In Progress Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatu
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Hi All, I'd confirmed this issue is be fixed by gdm3 3.36.3-0ubuntu0.20.04.1 and passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. The environment: kernel: 5.4.0-47-generic gdm3: 3.36.3-0ubuntu0.20.04.1 nvidia-driver-440: 440.100-0ubuntu0.20.04.1 GPU: VGA compatible controller [0300]: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] ** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Fix Committed Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in gdm3 source package in Focal: Fix Committed Status in gnome-session source package in Focal: Invalid Status in grub2 source package in Focal: Invalid Status in nvidia-graphics-drivers-390 source package in Focal: Invalid Status in nvidia-graphics-drivers-430 source package in Focal: Invalid Status in nvidia-graphics-drivers-435 source package in Focal: Invalid Status in nvidia-graphics-drivers-440 source package in Focal: Invalid Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVI
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** No longer affects: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
@Marco, Hi, here is the steps when verifying mutter from focal-proposed: 1. Upgrade all packages to latest version in focal-updates. 2. Enable focal-proposed in source list 3. sudo apt install mutter 4. Configure external screen orientation by selecting "Portrait Right" 5. Screen orientation doesn't change but asking save changes. 6. Press "Revert changes" 7. Configure external screen orientation by selecting "Portrait Right" again. 8. Screen goes to black screen. Attachment is the journal log. ``` Jul 24 03:02:18 u kernel: show_signal_msg: 38 callbacks suppressed Jul 24 03:02:18 u kernel: gnome-control-c[3252]: segfault at 7fff58ce6ff8 ip 7fa5ef8b114c sp 7fff58ce7000 error 6 in libc-2.31.so[7fa5ef841000+178000] Jul 24 03:02:18 u kernel: Code: 1f 80 00 00 00 00 e8 b3 bb ff ff eb d1 90 f3 0f 1e fa 48 85 d2 0f 84 63 01 00 00 41 57 49 89 ff 41 56 49 89 d6 41 55 49 89 d5 <41> 54 4c 8d 25 4b 77 15 00 55 48 8d 2d ab 84 15 00 53 4c 29 e5 48 ``` ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874567/+attachment/5395509/+files/journal.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.boa
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I tried to install stock 20.04.1 ubuntu with 'Install third party pkgs (e.g. nvidia)' + enable login automatically. After a reboot because of installation completed, the system will stuck in GDM login screen and can't login even if typing correct password. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-g
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: oem-priority Status: Triaged => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
[Summary] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1. Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically". 2. Install with default options 2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2 Enable "Login automatically" from system settings. After reboot, the system won't login automatically even can not login manually. [Environment] HP Z4 G4 Workstation + RTX6000 (10de:1e30) [Solution] Tried to patch the solution from comment#119 as a debian package[2]. The problem is solved. (Verified in scenario 2) [1] sha256sum ``` $ sha256sum ~/Downloads/groovy-desktop-amd64.iso bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 /home/jeremysu/Downloads/groovy-desktop-amd64.iso ``` [2] gdm3 from https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.ve
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Here is the debdiff. ** Patch added: "gdb3~oem-1891965.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405674/+files/gdb3~oem-1891965.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
[Summary] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1. Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically". 2. Install with default options 2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2 Enable "Login automatically" from system settings. After reboot, the system won't login automatically even can not login manually. [Environment] HP Z4 G4 Workstation + RTX6000 (10de:1e30) [Solution] Tried to patch the solution from comment#119 as a debian package[2]. The problem is solved. (Verified in scenario 2) The debdiff as attachment, please help to review. [1] sha256sum ``` $ sha256sum ~/Downloads/groovy-desktop-amd64.iso bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 /home/jeremysu/Downloads/groovy-desktop-amd64.iso ``` [2] gdm3 from https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801/+packages ** Description changed: [ Impact ] - In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. + In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] - 1. Boot ubuntu into desktop environment. - 2. Enabled auto login in System->Users - 3. Reboot the system + Here are two scenario of auto login with groovy (20.10) daily build[1]: + + 1) Checked "Install third-party software" (e.g. nvidia-driver) with + enabling "Login automatically" during installation. + + 2) Install groovy daily build with default options, after installation completed: + 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. + 2.2) Enable "Login automatically" from system settings. + + Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] - Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. + Low, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. - PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 + [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 + [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 + [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
[Summary] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1. Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically". 2. Install with default options 2.1 Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2 Enable "Login automatically" from system settings. After reboot, the system won't login automatically even can not login manually. [Environment] HP Z4 G4 Workstation + RTX6000 (10de:1e30) [Solution] Tried to patch the solution from comment#119 as a debian package[2]. The problem is solved. (Verified in scenario 2) The debdiff as attachment, please help to review. [1] sha256sum ``` $ sha256sum ~/Downloads/groovy-desktop-amd64.iso bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 /home/jeremysu/Downloads/groovy-desktop-amd64.iso ``` [2] gdm3 from https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801/+packages ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405700/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Changed in: oem-priority Status: Confirmed => Triaged ** Attachment removed: "gdb3~oem-1891965.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405674/+files/gdb3~oem-1891965.debdiff ** Attachment removed: "gdb3~oem-1891965.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405678/+files/gdb3~oem-1891965.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I'd updated the debdiff to insert a DEP-3 header. Here is the new debdiff. ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5406013/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405700/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Description changed: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] - Low, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. + Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPRO
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: oem-priority Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: In Progress Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.ch
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Update for summarizing current symptoms and workaround solution:
[Steps to reproduce]
1. Enable auto login through GUI ("Settings"->"Users"->"Automatic Login" to
enable)
2. reboot
3. system stop at gdm login screen
There are two symptom I found currently:
4.1 enter correct password is not able to login
4.2 enter correct password manually and it can login
[Workaround]
Here are two workaround solution from comment#31 and comment#71:
1. Removing 'splash' from kernel command line
2. Adding 'nvidia-drm.modeset=1' in kernel command line
[Environments]
product: Lenovo ThinkStation P720[1]
bios-version: S04KT41A
CPU: Intel(R) Xeon(R) Gold 6240C CPU @ 2.60GHz (72x)
GPU: 18:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106GL
[Quadro P2000] [10de:1c30] (rev a1)
kernel-version: 5.6.0-1010-oem
nvidia-driver: nvidia-driver-440
[1]
https://www.lenovo.com/gb/en/workstations/p-series/ThinkStation-P720/p/33TS3TPP720
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing gnome-session-binary fixes it, or just not using automatic
login.
Status in OEM Priority Project:
New
Status in gdm3 package in Ubuntu:
Confirmed
Status in gnome-session package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in gdm3 source package in Eoan:
Confirmed
Status in gnome-session source package in Eoan:
Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Bug description:
I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
login screen (which I shouldn't; I have auto login enabled), and
logging in just takes me back to the same user selection screen even
though the password is correct.
If I switch to a TTY and run `sudo pkill gnome-session-binary`,
logging in through GDM starts working again.
I should add that the do-release-upgrade was rocky; I did it in a
terminal from within gnome, went away for a while, and when I
returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
dpkg --configure -a` and complete the upgrade, but I don't know if
something's still messed up due to that.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57
CDT 2019
GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 28 19:55:42 2019
DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if
00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
InstallationDate: Installed on 2019-09-14 (13 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: MSI MS-7A67
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.60
dmi.board.asset.tag: Default string
dmi.board.name: H270I GAMING PRO AC (MS-7A67)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7A67
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
version.li
[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap
** Tags added: originate-from-1898665 stella -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873184 Title: Wired and wireless connection details have not enough height and items overlap Status in gnome-control-center: Unknown Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Status in gnome-control-center source package in Groovy: Fix Released Bug description: * Impact The details of the connection settings sometime overlap * Test case Connect the computer to a wired ethernet, go to settings and check the connection details, the items should be displayed separated and not overlapping * Regression potential Check that the connection details dialog is correctly displayed on different typo of connections, the change is in the layout of the elements so it could impact the layout in other cases To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902464] [NEW] The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time
Public bug reported: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. ** Affects: oem-priority Importance: Undecided Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1900094 sutton ** Tags added: oem-priority originate-from-1900094 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1902464/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time
** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1902464/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time
** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Summary changed: - The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time + The rear panel of Lenovo P620 doesn't support more than one audio device at the same time -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1902464/+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 1871471] Re: flash end of life soon, suggest remove from hirsute and also handle stable releases
Verified by using 1.8.8~ubuntu18.04.1. The 4 hours hang issue is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute and also handle stable releases Status in OEM Priority Project: Fix Released Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Status in adobe-flashplugin source package in Xenial: Fix Released Status in flashplugin-nonfree source package in Xenial: Fix Released Status in pepperflashplugin-nonfree source package in Xenial: Fix Released Status in adobe-flashplugin source package in Bionic: Fix Released Status in flashplugin-nonfree source package in Bionic: Fix Released Status in pepperflashplugin-nonfree source package in Bionic: Fix Released Status in adobe-flashplugin source package in Focal: Fix Released Status in flashplugin-nonfree source package in Focal: Fix Released Status in pepperflashplugin-nonfree source package in Focal: Fix Released Status in adobe-flashplugin source package in Groovy: Fix Released Status in pepperflashplugin-nonfree source package in Groovy: Fix Released Status in adobe-flashplugin source package in Hirsute: Fix Released Status in pepperflashplugin-nonfree source package in Hirsute: Confirmed Status in pepperflashplugin-nonfree package in Debian: Unknown Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+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 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
** Changed in: oem-priority Status: Triaged => Fix Committed -- 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/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Committed Status in ubiquity package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Triaged Status in ubuntu-drivers-common source package in Groovy: New Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
Verified by using 'focal-desktop-amd64.iso' from http://cdimage.ubuntu.com/focal/daily-live/pending/ SHA256 e2ce1771e352b04cfdef5bf6583f6a7d62b1f2967903fae512506d18d251a434 *focal-desktop-amd64.iso $ sha256sum focal-desktop-amd64.iso e2ce1771e352b04cfdef5bf6583f6a7d62b1f2967903fae512506d18d251a434 focal-desktop-amd64.iso ** 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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Triaged Status in ubuntu-drivers-common source package in Groovy: New Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1917010] [NEW] Hard to detect double-clicks on the HiDPI touchscreen system
Public bug reported: Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Triaged ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1898663 stella ** Tags added: oem-priority originate-from-1898663 stella ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: New Bug description: Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1917010/+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 1929371] [NEW] [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: In Progress ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1884497 sutton ** Summary changed: - there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged + [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged ** Tags added: oem-priority originate-from-1884497 sutton ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: New Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
@Seb, I'll work on these two patches comment#3 mentioned in the other bug. https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929371 Let's leave this ticket to track https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For focal ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500202/+files/alsa-ucm-conf_1.2.2-1ubuntu0.8.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For groovy ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu5.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500204/+files/alsa-ucm-conf_1.2.2-1ubuntu5.3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
alsa-ucm-conf/h/i already contains this patch https://github.com/alsa- project/alsa-ucm-conf/commit/368f10bdc3dbfd4f83ab348b54b8455f08fd1a9e. Thus, skip. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For impish ** Patch added: "pulseaudio_14.2-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500205/+files/pulseaudio_14.2-2ubuntu2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For hirsute ** Patch added: "pulseaudio_14.2-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500206/+files/pulseaudio_14.2-1ubuntu2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For groovy ** Patch added: "pulseaudio_13.99.2-1ubuntu2.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500217/+files/pulseaudio_13.99.2-1ubuntu2.4.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For focal ** Patch added: "pulseaudio_13.99.1-1ubuntu3.11.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500253/+files/pulseaudio_13.99.1-1ubuntu3.11.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
Hi Daniel,
SRU template filled, thanks!
** Description changed:
[Impact]
+ In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
+
+ In this case, the rear Mic will present on input devices of "Sound
+ Settings" even if attaching nothing to rear mic jack.
[Fix]
+ For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
+ ```
+ control.18 {
+ iface CARD
+ name 'Rear Mic Jack'
+ value true
+ comment {
+ access read
+ type BOOLEAN
+ count 1
+ }
+ }
+ ```
+ After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
+
+ For pulseaudio, if there is no any audio devices attached, then
+ attaching an input device on rear mic jack. The port will not be
+ selected automatically because the profiles is off. It needs patch
+ pulseaudio to check off profiles (for dual codec case).
[Test]
+ After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
+ This change only apply the bonus on below cases:
+ ```
+ if ((has_input_port && found_available_input_port && !has_output_port) ||
+ (has_output_port && found_available_output_port && !has_input_port) ||
+ (has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
+ ```
+ and these cases have been tested.
+ If there are some complex codec design then it might cause problem but so far
we didn't see that.
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Triaged
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Incomplete
Status in alsa-ucm-conf source package in Focal:
New
Status in pulseaudio source package in Focal:
New
Status in alsa-ucm-conf source package in Groovy:
New
Status in pulseaudio source package in Groovy:
New
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
New
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Tags added: originate-from-1929152 stella -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
``` Mar 3 18:07:02 kernel: [ 4935.420223] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:07:16 kernel: [ 4949.440656] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:08:11 kernel: [ 5004.462545] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:09:14 kernel: [ 5066.643244] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:09:34 kernel: [ 5087.214632] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:26 kernel: [10538.987863] gnome-terminal- invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:28 kernel: [10541.043501] gnome-terminal- invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:45 kernel: [10558.082088] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:49 kernel: [10562.058290] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:14 kernel: [10586.699020] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:35 kernel: [10608.175575] gnome-shell invoked oom-killer: gfp_mask=0x0(), order=0, oom_score_adj=0 Mar 3 19:41:55 kernel: [10627.942562] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:55 kernel: [10628.294303] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:42:12 kernel: [10645.292252] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:42:43 kernel: [10675.670335] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:06 gnome-shell[1691]: GNOME Shell crashed with signal 6 Mar 3 19:43:15 kernel: [10708.155220] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:31 kernel: [10724.420148] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:32 kernel: [10725.336522] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:36 kernel: [10729.101114] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:44 kernel: [10737.358855] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:44:09 kernel: [10761.733283] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:44:31 kernel: [10783.687545] pool-gnome-shel invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:45:23 /usr/lib/gdm3/gdm-x-session[1425]: (EE) Caught signal 6 (Aborted). Server aborting ``` Does not make sense to me, I don't think it's DM/WM issue but tool issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modeset
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
@Timo, I guess you could get passed if adding "--oomable" ** Also affects: plainbox-provider-checkbox Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Tags added: originate-from-1932285
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
Fix Committed
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions
--
Mailing list: https://launchpad.net/~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 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode
** Tags added: originate-from-1934872 stella -- 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/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Committed Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1936302] [NEW] To support elanmoc driver
Public bug reported: The upstream already accept the Elan fingerprint support. https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/278 ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1936302 Title: To support elanmoc driver Status in libfprint package in Ubuntu: New Bug description: The upstream already accept the Elan fingerprint support. https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/278 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1936302/+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 1936885] [NEW] Crash Report pop-up after switch graphic mode via nvidia-setting
Public bug reported: [Summary] Switch graphic mode from powesaving to performance mode via nvidia-setting, a crash report msg pop-up [Steps to reproduce] 1) install pc-stella-cmit-focal-amd64-X00-20210426-1500 and boot into OS 2) swtich graphic mode from performance to powersaving via nvidia-setting --> works well 3) reboot 4) swtich graphic mode from powesaving to performance mode via nvidia-setting [Expected result] no crash report pop-up [Actual result] Switch graphic mode from powesaving to performance mode via nvidia-setting, a crash report msg pop-up -- [ 58.006598] nvidia-settings[2364]: segfault at 20016 ip 7fafc7b0f160 sp 7ffebfe9d818 error 4 in libgobject-2.0.so.0.6400.6[7fafc7ae1000+36000] ** Affects: oem-priority Importance: Undecided Status: New ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1927183 stella ** Tags added: oem-priority originate-from-1927183 stella -- 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/1936885 Title: Crash Report pop-up after switch graphic mode via nvidia-setting Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] Switch graphic mode from powesaving to performance mode via nvidia-setting, a crash report msg pop-up [Steps to reproduce] 1) install pc-stella-cmit-focal-amd64-X00-20210426-1500 and boot into OS 2) swtich graphic mode from performance to powersaving via nvidia-setting --> works well 3) reboot 4) swtich graphic mode from powesaving to performance mode via nvidia-setting [Expected result] no crash report pop-up [Actual result] Switch graphic mode from powesaving to performance mode via nvidia-setting, a crash report msg pop-up -- [ 58.006598] nvidia-settings[2364]: segfault at 20016 ip 7fafc7b0f160 sp 7ffebfe9d818 error 4 in libgobject-2.0.so.0.6400.6[7fafc7ae1000+36000] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936885/+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 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode
** Tags added: originate-from-1934702 -- 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/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Since alsa-ucm-conf is updated by following the upstream version. ``` commit aa74f4c12eefcc98582572d2fc48982cf7478b51 (tag: pkg/import/1.2.4-1) Author: Jordi Mallach Date: Mon Dec 7 22:13:23 2020 +0100 1.2.4-1 (patches unapplied) Imported using git-ubuntu import. Notes (changelog): * New upstream release. * Update Standards-Version to 4.5.1, with no changes needed. ``` Above commit already brought https://github.com/alsa-project/alsa-ucm- conf/tree/master/ucm2/USB-Audio for P620 parts. ** Changed in: alsa-ucm-conf (Ubuntu) Assignee: Hui Wang (hui.wang) => (unassigned) ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Released ** Description changed: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio + [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
@Seb, do you think I can work on SRU https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 these two patches? since the #290 patch seems like still need a long time discussion on upstream and only this patch have high potential regression risk. so far I need to backport these three patches and maintain on our archive. If we could reduce the scope then it will be helpful in current situation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1923129] [NEW] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Public bug reported: Steps to produce this issue: 1. Install hirsute daily build (495fe189e32d873ba79d7753134c22353ea89e8e6d62498f6c825a5de6a8a4a7 *hirsute-desktop-amd64.iso) from https://cdimage.ubuntu.com/daily-live/current/ 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 Uname: Linux 5.10.0-1020-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 00:52:45 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210201-1380+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-03-03 (36 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210201-16:07 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=d0bd6ed9-a447-4115-9853-cbda6eea7e29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105+git2104080909.6b4e95~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2104080936.6528cd~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923129 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in xorg package in Ubuntu: New Bug description: Steps to produce this issue: 1. Install hirsute daily build (495fe189e32d873ba79d7753134c22353ea89e8e6d62498f6c825a5de6a8a4a7 *hirsute-desktop-amd64.iso) from https://cdimage.ubuntu.com/daily-live/current/ 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 Uname: Linux 5.10.0-1020-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 00:52:45 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210201-1380+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 0
[Desktop-packages] [Bug 1923153] [NEW] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Public bug reported: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal oem-priority originate-from-1916427 stella ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: H
[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
I tried to install hirsute daily build (495fe189e32d873ba79d7753134c22353ea89e8e6d62498f6c825a5de6a8a4a7) and didn't see this issue. but the xorg might have some problems when using hirsute. here is the result of $ xrandr -d :0 --prop --- PRIME Synchronization: 0 supported: 0, 1 GAMMA_LUT_SIZE: 4096 range: (0, -1) DEGAMMA_LUT_SIZE: 4096 range: (0, -1) GAMMA_LUT: 0 range: (0, 65535) CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 DEGAMMA_LUT: 0 range: (0, 65535) TearFree: auto supported: off, on, auto subconnector: HDMI supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled vrr_capable: 0 range: (0, 1) max bpc: 8 range: (8, 16) underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, on, auto scaling mode: None supported: None, Full, Center, Full aspect link-status: Good supported: Good, Bad CONNECTOR_ID: 80 supported: 80 non-desktop: 0 range: (0, 1) --- When issuing the same command on hirsute daily build, it shows --- non-desktop: 0 range: (0, 1) --- only. Tried packages from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers doesn't help. ** Tags added: oem-priority originate-from-1916427 stella ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N
[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
When I attached another monitor to dGPU (which means connecting monitor to each iGPU and dGPU), then there is no problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
BTW, the FPS is 1. $ DISPLAY=:0 glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 344 frames in 5.6 seconds = 61.884 FPS 5 frames in 5.0 seconds = 0.997 FPS 6 frames in 6.0 seconds = 1.002 FPS 6 frames in 6.0 seconds = 1.000 FPS --- I did confirm the i915(iGPU) + amdgpu(dGPU) could reproduce this issue as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Attachment added: "xrandr-verbose" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5485957/+files/xrandr-verbose -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
backport the patches from https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/460 doesn't help. --- * d5016e5b61f96496f9b31d14eae16f5f0148b748 (HEAD -> backport-7-patches-from-Łukasz-sync_present_to_slave_outputs) Remove unused function ms_covering_xf86_crtc() * d892481c2a3d67462f6d2c0d762c43b63cdcd45c xserver/output: rename some badly named variables/APIs. * 1fb0dc09a60e97306088d75fefeed17a39e622ea (master) modesetting: Remove few common functions from ms namespace * a1f28e05d602f5cde825111ca0654311c2aba73b modesetting: remove unnecessary ms_covering_xf86_crtc dup of ms_covering_randr_crtc * d1b3204d1f1357426864c5125bf2ff8b84827d23 modesetting: Find crtc on secondary outputs as fallback instead of returning primary crtc * 028688ba6dc50fbc6430812c608f69912e4196d4 randr: Fix link errors after previous commit * 327441e28fa50fef18c0d15f377e61479fa956a4 present: fix msc offset calculation in screen mode * 8477111ac5e3dee4066efc689d4507fa1b245900 present: Use crtc's screen present operation for syncing * c271560a66d1d0a36dd7b784e75822ee00acc216 modesetting: Initialize present extension despite glamor is disabled * 9f5b6b400462dd5b979c40361c4fcb35d08f9dd1 apt source xserver-xorg-core -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
@Daniel, ok, let me try the other desktops. BTW, the cursor moves smoothly but other operations laggy (e.g. move the terminal window). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
XFCE has the same result. I'm able to reproduce this issue on XFCE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923178] Re: synaptic fingerprint device(06cb:00df) doesn't work on focal
** Changed in: libfprint (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1923178 Title: synaptic fingerprint device(06cb:00df) doesn't work on focal Status in OEM Priority Project: Invalid Status in libfprint package in Ubuntu: Invalid Bug description: [Release] Focal - 20.04 [libfprint version] 1:1.90.2+tod1-0ubuntu1 [Device] ZBook Studio G7 [BIOS version] S91 Ver. 01.04.01 [Fingerprint reader] 06cb:00df Synaptics, Inc. [Fingerprint reader firmware version] 10.01.3273255 [Expected] Enroll fingerprint successfully. [Result] When enrolling new finger, settings will pop up "Failed to enroll new fingerprint". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923178/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Although comment#2 is merged, this issue still needs PA corresponding (https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290). Therefore, we will deliver a special alsa-ucm-conf on our oem-archive as short-term solution and leave it be replaced after this ticket gets the merge. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
here is the output ** Attachment added: "journal-b-k.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486865/+files/journal-b-k.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Attachment added: "lspci2.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486866/+files/lspci2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Attachment added: "journal2.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486867/+files/journal2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
@Daniel, Above are the outputs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, The "AMD R7 430" is the product name of the graphic card. https://ssl.www8.hp.com/emea_africa/en/products/oas/product-detail.html?oid=26185185 I guess it's related to radeon driver since we could see this issue with amd RX550 as well. ** Tags added: originate-from-1923120 ** Tags added: originate-from-1921875 -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
BTW, for i915 case, it's not 100% reproduce if the boot-vga-device is i915. Which means in Intel + AMD platform. Sometime the system laggy when output from dGPU (AMD 430). Sometime the system laggy when output from iGPU (intel) AFTER switching the monitor between dGPU and iGPU (e.g. boot vga: i915 -> moving monitor to dGPU -> moving monitor back to iGPU). but all works smoothly when connecting two monitor from both iGPU and dGPU (this scenario works good on AMD + AMD platform). -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
The other finding for comment#20. If connecting two monitors then there is a way to reproduce it. 1. Set iGPU as primary monitor 2. Run an application from secondary display (dGPU) (e.g. glxgear) 3. Moving the application from secondary display (dGPU) to primary display (iGPU) then the issue occur. For comment#19, I'm preparing hirsute using today daily build. Will update the result here later. -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, I could reproduce this issue when using today hirsute daily build $ sha256sum ~/Downloads/hirsute-desktop-amd64.iso 4908a5c919f4b796a856be69a044334eb1a910727180618348db0a8a1ef70360 /home/jeremysu/Downloads/hirsute-desktop-amd64.iso after switching back to xorg (hirsute default uses Wayland) -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Changed in: oem-priority Status: Confirmed => In Progress -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, Thanks for sharing comment#27. Let me summarize the reproduce scenarios in Intel + AMD case. 1. Boot from iGPU -> switch to dGPU -> switch back to iGPU -> iGPU lag. 2. Boot from iGPU -> connect secondary monitor to dGPU -> remove 1st monitor from iGPU -> dGPU lag. 3. Boot from iGPU -> connect secondary monitor to dGPU -> set iGPU as primary display -> moving an application (e.g. glxgear) from secondary display (dGPU) to primary display (iGPU) -> iGPU lag. The comment#27 could workaround case#1 and case #3. but switch to wayland could fix these three cases. -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
@Daniel, u@u-HP-EliteDesk-800-G6-Tower-PC:~$ dpkg -S /usr/share/X11/xorg.conf.d/10-radeon.conf xserver-xorg-video-radeon: /usr/share/X11/xorg.conf.d/10-radeon.conf u@u-HP-EliteDesk-800-G6-Tower-PC:~$ dpkg -S /usr/share/X11/xorg.conf.d/10-amdgpu.conf xserver-xorg-video-amdgpu: /usr/share/X11/xorg.conf.d/10-amdgpu.conf The radeon and amdgpu drivers are came from xserver-xorg-video- radeon/amdgpu. xserver-xorg-video-radeon comes from xserver-xorg-video-ati xserver-xorg-video-ati and xserver-xorg-video-amdgpu comes from xserver-xorg-video-all Do you think we could remove both from xserver-xorg-video-all if the target is to use modesetting for amd gpu? Or anything I can do to help to fix it? -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, Thank you for sharing. OEM team is not allow the provide a customization as workaround before we don't know the plan to fix. I reported an issue as https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194 ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues #194 https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194 -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, Thank you for sharing. We are not allow to provide a customization as workaround before we know the fix plan. I reported an upstream issue: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194 -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Changed in: oem-priority Status: In Progress => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-driver-ati: Unknown Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1963701] [NEW] [NVIDIA][Wayland] graphic target not able to reach
Public bug reported: [Steps to reproduce] 1. Have an I+N desktop. 2. Attach monitor to dGPU (nvidia) 3. install jammy daily build with enable third-party (to install nvidia-510) 4. dist-upgrade 5. reboot the system and make sure the system starts with Wayland [Expected result] System launch gdm login screen without problem [Actual result] System stuck with blackscreen [Other information] $ systemctl list-jobs JOB UNIT TYPE STATE 140 system-getty.slice start waiting 2 multi-user.targetstart waiting 1 graphical.target start waiting 165 plymouth-quit-wait.service start running 8 setvtrgb.service start waiting 110 systemd-update-utmp-runlevel.service start waiting 6 jobs listed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 [modified: lib/udev/rules.d/61-gdm.rules] ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 5 00:15:24 2022 InstallationDate: Installed on 2022-01-20 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220109) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-03-04T20:36:36.997559 ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority originate-from-1956556 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: New Bug description: [Steps to reproduce] 1. Have an I+N desktop. 2. Attach monitor to dGPU (nvidia) 3. install jammy daily build with enable third-party (to install nvidia-510) 4. dist-upgrade 5. reboot the system and make sure the system starts with Wayland [Expected result] System launch gdm login screen without problem [Actual result] System stuck with blackscreen [Other information] $ systemctl list-jobs JOB UNIT TYPE STATE 140 system-getty.slice start waiting 2 multi-user.targetstart waiting 1 graphical.target start waiting 165 plymouth-quit-wait.service start running 8 setvtrgb.service start waiting 110 systemd-update-utmp-runlevel.service start waiting 6 jobs listed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 [modified: lib/udev/rules.d/61-gdm.rules] ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 5 00:15:24 2022 InstallationDate: Installed on 2022-01-20 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220109) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-03-04T20:36:36.997559 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+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 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Tags removed: gdm3
** Tags added: nvidia
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
New
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Status in gdm3 source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in gdm3 source package in Impish:
New
Status in ubuntu-drivers-common source package in Impish:
In Progress
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
To manage notifi
