[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 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 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 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 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 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 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
** 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
** 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 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 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 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 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 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 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:
- 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
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
** 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 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 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: "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] [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 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 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 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 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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1992736
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1992116
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu
[Desktop-packages] [Bug 1990341] [NEW] [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
Public bug reported:
> 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.
** Affects: oem-priority
Importance: High
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => 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:
[FeatureFreeze Exceptions] Support to install nvidia driver by
allowing list
Status in OEM Priority Project:
Confirmed
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
[Desktop-packages] [Bug 1990262] Re: Screen reset randomly when moving cursors
** Attachment added: "sosreport-ubuntu-2022-09-07-zluxqrd.tar" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+attachment/5617344/+files/sosreport-ubuntu-2022-09-07-zluxqrd.tar -- 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/1990262 Title: Screen reset randomly when moving cursors Status in mutter package in Ubuntu: New Bug description: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+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 1990262] Re: Screen reset randomly when moving cursors
** Attachment added: "20220907_145805.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+attachment/5617343/+files/20220907_145805.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/1990262 Title: Screen reset randomly when moving cursors Status in mutter package in Ubuntu: New Bug description: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+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 1990262] [NEW] Screen reset randomly when moving cursors
Public bug reported: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1990262 Title: Screen reset randomly when moving cursors Status in mutter package in Ubuntu: New Bug description: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
The correct fix should in kernel driver or GPU firmware.
Please track on drm-intel#6851.
** Changed in: oem-priority
Status: In Progress => Incomplete
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescr
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Attachment added: "ftrace-when-issue-happening"
https://bugs.launchpad.net/bugs/1990089/+attachment/5616861/+files/ftrace-when-issue-happening
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in OEM Priority Project:
In Progress
Status in linux package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
New
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Attachment added: "strace-when-issue-happening"
https://bugs.launchpad.net/bugs/1990089/+attachment/5616860/+files/strace-when-issue-happening
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in OEM Priority Project:
In Progress
Status in linux package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
New
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1982914 stella
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in OEM Priority Project:
In Progress
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerv
[Desktop-packages] [Bug 1990089] [NEW] Screen freeze when performing memory stress in Wayland mode
Public bug reported:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419,
fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, argc=1,
argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-chansey+X25
InstallationDate: Installed on 2022-09-06 (12 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: oem-priority
Importance: Critical
Assignee: jeremyszu (os369510)
[Desktop-packages] [Bug 1988245] Re: [Feature] A way to install nvidia driver for development
MP is here https://github.com/tseliot/ubuntu-drivers-common/pull/71 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988245 Title: [Feature] A way to install nvidia driver for development Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Description] OEM/ODM/CE/IHV partners need to have a standardize way to install nvidia drivers which way needs to make sure the configuration is same as what the end user will use. As u-d-c has some configuration during the installation, we would like to have a way to install nvidia drivers correctly for the business. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1988245/+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 1988245] [NEW] [Feature] A way to install nvidia driver for development
Public bug reported: [Description] OEM/ODM/CE/IHV partners need to have a standardize way to install nvidia drivers which way needs to make sure the configuration is same as what the end user will use. As u-d-c has some configuration during the installation, we would like to have a way to install nvidia drivers correctly for the business. ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Assignee: jeremyszu (os369510) Status: New ** Tags: jammy oem-priority ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => jeremyszu (os369510) -- 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/1988245 Title: [Feature] A way to install nvidia driver for development Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Description] OEM/ODM/CE/IHV partners need to have a standardize way to install nvidia drivers which way needs to make sure the configuration is same as what the end user will use. As u-d-c has some configuration during the installation, we would like to have a way to install nvidia drivers correctly for the business. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1988245/+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
After some checks, it seems because data_device_start_drag() doesn't support MetaWaylandTouch. The fix will impact the mutter architecture and it's more likely a feature request in mutter so far. It can be workaround by either sync MetaWaylandPointer motion and MetaWaylandTouch when meta_wayland_seat_update() or meta_wayland_seat_handle_event() with some tweaks. or some changes in meta_wayland_data_device_start_drag(). As maintainer mentions[1] the drag feature is refactoring part.1: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2068 part.2: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2099 part.3: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2100 and this issue might be fixed in part.5... For both workaround look not suitable with the maintainer's design. I prefer to wait until the refactoring completed by maintainer. [1] https://gitlab.gnome.org/GNOME/mutter/-/issues/2393#note_1532698 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2393 https://gitlab.gnome.org/GNOME/mutter/-/issues/2393 ** Changed in: oem-priority Assignee: jeremyszu (os369510) => (unassigned) -- 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: Unknown 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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2025 https://gitlab.gnome.org/GNOME/mutter/-/issues/2025 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2025 Importance: Unknown Status: Unknown -- 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: Unknown 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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Also affects: gnome-shell-extension-desktop-icons-ng Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell-extension-desktop-icons-ng -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: Confirmed Status in gnome-shell-extension-desktop-icons-ng 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/oem-priority/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: Confirmed 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/oem-priority/+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 1982472] Re: Support A+N platform
https://github.com/tseliot/nvidia-settings/pull/14 for nvidia-settings UI. -- 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/1982472 Title: Support A+N platform Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Bug description: The 'Power Saving Mode' of Nvidia app should change to ATI when the integrated graphic is Advanced Micro Devices. [Steps to reproduce] 1. Install the OEM image 2. Boot and log 3. 'Dash' -> 'Nvidia Settings' 4. Verify the 'PRIME Profiles' [Expected result] Nvidia (Performance Mode) Nvidia On-Demand AMD (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query [Actual result] Nvidia (Performance Mode) Nvidia On-Demand Intel (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|intel|on-demand|query [Failure rate] 100% [Other Information] ubuntu 22.04 nvidia-prime 0.8.17.1 nvidia-settings 510.47.03-0ubuntu1 nvidia-driver 510.73.05-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1982472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
Installed a package from a PPA won't break the package upgrade. As Timo uploads the package to Unstable. If everything goes smoothly, the next version of xserver-xorg-video-amdgpu will contain the patches and that version will overwrite mine from the PPA. In short, an "apt upgrade" will overwrite it and point to current version from ubuntu-archive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982472] Re: Support A+N platform
FWIK, there are many related packages need to modify together since it's
similar to an interface change.
It'll be more reasonable if we target to Jammy+.
The power-saving mode in Jammy is almost useless (but the nvidia-340, 390 may
still need it).
However, the 'power-saving' mode apply:
```
"Section \"ServerLayout\"\n"
"Identifier \"layout\"\n"
"Option \"AllowNVIDIAGPUScreens\"\n"
"EndSection\n\n");
```
and disable nvidia driver.
If so, then I think we could say it's "non-nvidia" ("no-nvidia", etc..) instead
of "intel" or "amd".
Which will more suitable when multiple graphic cards are attached.
Hi Alberto,
Have you any comment on this?
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** 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 nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1982472
Title:
Support A+N platform
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
New
Status in nvidia-settings package in Ubuntu:
New
Bug description:
The 'Power Saving Mode' of Nvidia app should change to ATI when the
integrated graphic is Advanced Micro Devices.
[Steps to reproduce]
1. Install the OEM image
2. Boot and log
3. 'Dash' -> 'Nvidia Settings'
4. Verify the 'PRIME Profiles'
[Expected result]
Nvidia (Performance Mode)
Nvidia On-Demand
AMD (Power Saving Mode)
u@Thor-P3-AMD-2:~$ prime-select
Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query
[Actual result]
Nvidia (Performance Mode)
Nvidia On-Demand
Intel (Power Saving Mode)
u@Thor-P3-AMD-2:~$ prime-select
Usage: /usr/bin/prime-select nvidia|intel|on-demand|query
[Failure rate]
100%
[Other Information]
ubuntu 22.04
nvidia-prime 0.8.17.1
nvidia-settings 510.47.03-0ubuntu1
nvidia-driver 510.73.05-0ubuntu0.22.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1982472/+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 1982472] Re: Support A+N platform
** Tags added: jammy -- 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/1982472 Title: Support A+N platform Status in OEM Priority Project: New Status in nvidia-prime package in Ubuntu: New Bug description: The 'Power Saving Mode' of Nvidia app should change to ATI when the integrated graphic is Advanced Micro Devices. [Steps to reproduce] 1. Install the OEM image 2. Boot and log 3. 'Dash' -> 'Nvidia Settings' 4. Verify the 'PRIME Profiles' [Expected result] Nvidia (Performance Mode) Nvidia On-Demand AMD (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query [Actual result] Nvidia (Performance Mode) Nvidia On-Demand Intel (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|intel|on-demand|query [Failure rate] 100% [Other Information] ubuntu 22.04 nvidia-prime 0.8.17.1 nvidia-settings 510.47.03-0ubuntu1 nvidia-driver 510.73.05-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1982472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
Hi Josh, In my experience on this issue, there are at least two ways to reproduce this issue. 1. fresh install. 2. enable "FRAMEBUFFER=y" in initramfs. As lenovo z16 is an AMD platform, would you please try to upgrade all packages to latest and try the package from the ppa of comment#62? BTW, FWIK, the Jammy is default to Wayland for AMD platform. I didn't see this issue on Wayland platform unless you switched to Xorg manually. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
The xserver-xorg-video-amdgpu patches #63~#66 don't need in focal because only Stock Jammy default installation will be affect. The same symptom can be reproduced in both Focal and Jammy with applying "FRAMEBUFFER=y" and the xserver-xorg-video-amdgpu patchset don't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
More precisely, it seems related to FRAMEBUFFER=y in "conf-hooks.d/cryptsetup". When I marked it as 'n', then issue is gone. Need to figure it out what's it exactly causes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
In Focal Stock Ubuntu, I confirmed if user installs "cryptsetup- initramfs" on I+A platform with choosing display mode to "External Only", the issue presents. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
comment#63-66 for xserver-xorg-video-amdgpu on Jammy. For debian and KKK, do we plan those to be landed through stable updates? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Committed Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Patch added: "0004-Do-not-consider-disabled-crtc-anymore-when-looking-f.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601763/+files/0004-Do-not-consider-disabled-crtc-anymore-when-looking-f.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Committed Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Patch added: "0001-amdgpu-fixup-driver-for-new-X-server-ABI.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601760/+files/0001-amdgpu-fixup-driver-for-new-X-server-ABI.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Committed Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Patch added: "0003-Prefer-crtc-of-primary-output-for-synchronization-wh.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601762/+files/0003-Prefer-crtc-of-primary-output-for-synchronization-wh.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Committed Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Patch added: "0002-Use-randr_crtc_covering_drawable-used-in-modesetting.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875015/+attachment/5601761/+files/0002-Use-randr_crtc_covering_drawable-used-in-modesetting.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Committed Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
I can confirmed the commits from https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/merge_requests/75/commits fix my issue on I+A machine using Jammy and KKK daily build. Test PPA is https://launchpad.net/~os369510/+archive/ubuntu/lp1875015 For Focal, it seems the extra patches are needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Committed Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Aleksandr, sound more likely the other issue. Since this issue is fixed, could you please report the other with attaching logs? -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: New Status in OEM Priority Project: Fix Released Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-495 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1967843] Re: cheese display corrupted under Ubuntu 22.04
I can confirmed the original issue gone after installing the version from comment#37 ** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in Cheese: Fix Released Status in OEM Priority Project: Fix Released Status in cheese package in Ubuntu: Invalid Status in clutter-gst-3.0 package in Ubuntu: Fix Released Status in clutter-gst-3.0 source package in Jammy: Fix Released Bug description: Impact == The cheese app is unusable with color bands showing in the main view. This bug doesn't affect all webcams. It's unknown what percentage of webcams are affected. Test Case On a system that experiences this bug: Install the update Run the cheese app Verify that the main view shows what your webcam can see normally. Click the camera button in the bottom toolbar area. Check if the photo looks normal. You can find it in ~/Pictures/Webcam What Could Go Wrong === Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint clutter-gst has been archived by GNOME. (It's recommended for apps to use GTK4 instead of GTK3 + Clutter). That means it's not possible for this patch to be accepted upstream. Instead, distros like Arch Linux are applying this patch. This patch removes 2 renderers that don't work (RGBx and BGRx) but still keeps ones that do work: RGBA and BRGA. Original Bug Report === The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 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-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatu
[Desktop-packages] [Bug 1973604] Re: [nvidia340] display hangs 10s on boot with nvidia-340
Hi ysfr, Would you please help to test this version? https://launchpad.net/~os369510/+archive/ubuntu/lp1973604 -- 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/1973604 Title: [nvidia340] display hangs 10s on boot with nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Since ubuntu-drivers-common 1:0.9.0~0.20.04.6, system running kernel 5.4 & nvidia-340 will experience 10s useless delay on boot because gpu-manager is waiting for nvidia-drm to load & nvidia-drm is not built in with nvidia-340. Several legacy nvidia cards are stuck to nvidia-340 & Kernel 5.4 as detailled in: https://nvidia.custhelp.com/app/answers/detail/a_id/3142/%7E/support-timeframes-for-unix-legacy-gpu-releases See prior investigation in comments of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1973604/+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
looks like nvidia-drm is not built in nvidia-340.
could you report the other bug for it takes 10 seconds when booting in
nvidia-340?
and we can leave the information there.
--
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:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
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
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
nope, drm is not nvidia_drm.
I don't have 5.4 + nvidia-340 environment.
Thus, I would like to get more information from you.
Could you please share
1. dkms status
2. find /lib/modules/$(uname -r) -name 'nvidia*'
3. your "/var/lib/dkms/" probably have nvidia-340 build log with your current
kernel, could you please share the contents from the directory?
(e.g. /var/lib/dkms/tp_smapi/kernel-5.14.0-1036-oem-x86_64)
--
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:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
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
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
but it doesn't show in your lsmod.
how about `modinfo nvidia_drm`?
--
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:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
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
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
update:
no transition plan for nvidia-340.
Then let's see why your nvidia-drm gone.
--
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:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
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-
[Desktop-packages] [Bug 1973211] [NEW] [Retirement] Nvidia 340 is not longer support
Public bug reported: The Legacy version is nvidia-390 and will become nvidia-470. The nvidia-340 is not longer support. Use this kind of non-support version will likely conflict with newer design (e.g. from u-d-c, gdm). Please going to remove it. ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- 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/1973211 Title: [Retirement] Nvidia 340 is not longer support Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: The Legacy version is nvidia-390 and will become nvidia-470. The nvidia-340 is not longer support. Use this kind of non-support version will likely conflict with newer design (e.g. from u-d-c, gdm). Please going to remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1973211/+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
ok, I aware the `nvidia-drm` should support in nvidia-340.
Did you blacklist it?
Can you check the nvidia-drm whether presenting in your system?
you could probably found it under
find ... /lib/modules/$(uname -r)/...
--
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:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
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:
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Hi,
I aware you don't have "nvidia_drm" which is needed for gdm as well.
u-d-c was wait the "nvidia_drm" be probed and your nvidia driver is 340 is
quite old as what I known.
FWIK, the legacy driver should be nvidia-390 and the next is 470.
I wondering why nvidia-340 is not yet be transited to 390 or newer.
Hi Alberto,
Will nvidia-340 be transited?
--
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:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
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
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Hi, would you please share:
1. lspci -nvk
2. /var/log/gpu-manager.log
3. journalctl -b -k
4. dpkg -l | grep nvidia
5. lsmod | grep 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:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
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/wi
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
** 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/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 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 Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+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 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
** Tags added: originate-from-1969352 sutton -- 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/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 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: In Progress Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+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 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
Impish: 1:0.9.2.4~0.21.10.2 after upgrading: available: 510.60.02-0ubuntu0.21.10.2 (auto-install) ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish ** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 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: In Progress Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+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 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
Focal: 1:0.9.0~0.20.04.7 before upgrading: available: 470.103.01-0ubuntu0.20.04.1 (auto-install) after upgrading: available: 510.60.02-0ubuntu0.20.04.2 (auto-install) ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 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: In Progress Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+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
after upgrading to 42.0-1ubuntu7 and can not reproduce this issue (default X). Selected to Wayland can not reproduce this issue as well. ** Changed in: oem-priority Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Incomplete 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
Hi Macros, would you please share the output of `journalctl -b` when issuing happening? -- 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: Unknown Status in Mutter: Unknown 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.l
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Hi Marcos, For bug description: --- [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 --- It should be workaround by adding "NVreg_PreserveVideoMemoryAllocations". Would you please share $ cat /proc/driver/nvidia/params ? -- 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: Unknown Status in Mutter: Unknown 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 s
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
For comment#10: NVreg_TemporaryFilePath means to use the specific path, if you didn't specify it then it will default to use /tmp. (if your /tmp has enough space to use then it's fine) FWIK, the firefox is now from snap and the stable firefox is disable Wayland. Thus, it could be the other problem. --- For comment#11: Looks like the other issue, probably attach the log on a new bug report? -- 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: Unknown Status in Mutter: Unknown 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.fam
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Copied the finding from https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 since this bug is created long time. Pieces of log ``` 四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00: GPU-581d669f-ec00-4588-ca5f-15ab24136974 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: Shader Program Header 18 Error 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405840=0x8204 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405848=0x8000 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=1270, Graphics Exception: ChID 0010, Class c597, Offset , Data ``` For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. Tried 510.60 as well and the problem is persistent. ** Tags added: jiayi 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: Unknown Status in Mutter: Unknown 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.hando
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Also affects: oem-priority Importance: Undecided Status: New ** 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 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: Unknown Status in Mutter: Unknown 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
[Desktop-packages] [Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
Hi Michael, do you mean the patch to disable wayland on nVidia? -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time Status in OEM Priority Project: Incomplete Status in mutter package in Ubuntu: Incomplete 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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Fix Released Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1969142] Re: Display glitch after resume on Wayland if boot vga is nvidia
** Description changed: [Steps to reproduce] 1. Install Jammy and dist-ugprade 2. systemctl suspend 3. press power button to resume [Expect result] system resume smoothly [Actual result] display glitch (please see the attachment) + + Pieces of log + ``` + 四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00: GPU-581d669f-ec00-4588-ca5f-15ab24136974 + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: Shader Program Header 18 Error + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405840=0x8204 + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405848=0x8000 + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=1270, Graphics Exception: ChID 0010, Class c597, Offset , Data + ``` For GDM, it needs at least https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1429657 to protect issue happens. For Mutter, a related patch is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341/diffs could cover if nvidia is secondary GPU. For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 23:51:06 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-14T22:23:09.064003 -- 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/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Steps to reproduce] 1. Install Jammy and dist-ugprade 2. systemctl suspend 3. press power button to resume [Expect result] system resume smoothly [Actual result] display glitch (please see the attachment) Pieces of log ``` 四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00: GPU-581d669f-ec00-4588-ca5f-15ab24136974 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: Shader Program Header 18 Error 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405840=0x8204 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405848=0x8000 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=1270, Graphics Exception: ChID 0010, Class c597, Offset , Data ``` For GDM, it needs at least https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1429657 to protect issue happens. For Mutter, a related patch is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341/diffs could cover if nvidia is secondary GPU. For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 23:51:06 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-14T22:23:09.064003 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+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 1969142] Re: Display glitch after resume on Wayland if boot vga is nvidia
** Attachment added: "FD78E3EA-8F81-4B58-B27A-F864F5CA5480.jpg" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142/+attachment/5580753/+files/FD78E3EA-8F81-4B58-B27A-F864F5CA5480.jpg ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Steps to reproduce] 1. Install Jammy and dist-ugprade 2. systemctl suspend 3. press power button to resume [Expect result] system resume smoothly [Actual result] display glitch (please see the attachment) For GDM, it needs at least https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1429657 to protect issue happens. For Mutter, a related patch is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341/diffs could cover if nvidia is secondary GPU. For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 23:51:06 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-14T22:23:09.064003 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+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 1969142] [NEW] Display glitch after resume on Wayland if boot vga is nvidia
Public bug reported: [Steps to reproduce] 1. Install Jammy and dist-ugprade 2. systemctl suspend 3. press power button to resume [Expect result] system resume smoothly [Actual result] display glitch (please see the attachment) For GDM, it needs at least https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1429657 to protect issue happens. For Mutter, a related patch is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341/diffs could cover if nvidia is secondary GPU. For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 23:51:06 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-14T22:23:09.064003 ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy jiayi nvidia oem-priority wayland -- 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/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Steps to reproduce] 1. Install Jammy and dist-ugprade 2. systemctl suspend 3. press power button to resume [Expect result] system resume smoothly [Actual result] display glitch (please see the attachment) For GDM, it needs at least https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1429657 to protect issue happens. For Mutter, a related patch is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341/diffs could cover if nvidia is secondary GPU. For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 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-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 23:51:06 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-14T22:23:09.064003 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Confirmed the gnome will not crash but the system will back to gdm login screen in 1st hot-plugging. Report the bug https://bugs.launchpad.net/oem-priority/+bug/1969121 -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
Confirmed the gnome will not crash but the system will back to gdm login screen in 1st hot-plugging. Report the bug https://bugs.launchpad.net/oem-priority/+bug/1969121 ** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session Status in Mutter: Unknown Status in OEM Priority Project: Fix Released Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: This is on my weird desktop setup, with one monitor plugged into an AMD card and one into an NVIDIA card. When using the Wayland session, by default Shell will come up on the monitor connected to the AMD card, and the second (NVIDIA) monitor will be blank. Attempting to enable the second monitor in Display Settings will immediately and reproducibly crash gnome-shell. This is trivial for me to reproduce, so if you need patches tested I can easily do so. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2 Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 09:37:51 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-11-02 (125 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+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
** Description changed: [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] - the external port is connecting to dGPU. + 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) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Tags added: nvidia-wayland wayland wayland-session ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New 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 1969121] [NEW] System fallback to gdm login screen when hot-plugging a external monitor in 1st time
Public bug reported: [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) ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy jiayi nvidia nvidia-wayland oem-priority wayland wayland-session ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New 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 1968957] Re: Cheese displays red-green lines in 22.04
** Attachment added: "CheeseDebug.txt" https://bugs.launchpad.net/oem-priority/+bug/1968957/+attachment/5580566/+files/CheeseDebug.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1968957 Title: Cheese displays red-green lines in 22.04 Status in OEM Priority Project: Confirmed Status in cheese package in Ubuntu: New Bug description: [Steps to reproduce] 1. Launch cheese 1.1. $ cheese (cheese:5504): Gdk-WARNING **: 12:16:54.536: Native Windows taller than 65535 pixels are not supported Gdk-Message: 12:16:54.981: Error 71 (Protocol error) dispatching to Wayland display. 1.2. $ sudo cheese displays "red-green lines". [Expected result] Cheese app works normally. [Actual result] The cheese app doesn't work as normal on Jammy. [Additional information] 1. tried "ubuntu-bug ... cheese" and it seems display a video on cheese but same result (red-green lights). 2. I'm not able to use `ubuntu-bug` to report the bug because it shows not found ".cache/CheeseDebug.txt". I saw it under /root/. Will attach it. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy $ dpkg -l | grep "cheese\|wayland\|gtk" ii apport-gtk 2.20.11-0ubuntu81 all GTK+ frontend for the apport crash report system ii cheese 41.1-1build1 amd64tool to take pictures and videos from your webcam ii cheese-common 41.1-1build1 all Common files for the Cheese tool to take pictures and videos ii gir1.2-gtk-3.0:amd64 3.24.33-1ubuntu1 amd64GTK graphical user interface library -- gir bindings ii gir1.2-gtk-4.0:amd64 4.6.2+ds-1ubuntu2 amd64GTK graphical user interface library -- gir bindings ii gir1.2-gtksource-4:amd64 4.8.3-1 amd64gir files for the GTK+ syntax highlighting widget ii gir1.2-javascriptcoregtk-4.0:amd64 2.36.0-2ubuntu1 amd64JavaScript engine library from WebKitGTK - GObject introspection data ii gstreamer1.0-gtk3:amd641.20.1-1ubuntu1 amd64GStreamer plugin for GTK+3 ii gtk-update-icon-cache 3.24.33-1ubuntu1 amd64icon theme caching utility ii gtk2-engines-murrine:amd64 0.98.2-3build2 amd64cairo-based gtk+-2.0 theme engine ii gtk2-engines-pixbuf:amd64 2.24.33-2ubuntu2 amd64pixbuf-based theme for GTK 2 ii ibus-gtk:amd64 1.5.26-4 amd64Intelligent Input Bus - GTK2 support ii ibus-gtk3:amd641.5.26-4 amd64Intelligent Input Bus - GTK3 support ii ibus-gtk4:amd641.5.26-4 amd64Intelligent Input Bus - GTK4 support ii libavahi-ui-gtk3-0:amd64 0.8-5ubuntu5 amd64Avahi GTK+ User interface library for GTK3 ii libcanberra-gtk3-0:amd64 0.30-10ubuntu1 amd64GTK+ 3.0 helper for playing widget event sounds with libcanberra ii libcanberra-gtk3-module:amd64 0.30-10ubuntu1 amd64translates GTK3 widgets signals to event sounds ii libcheese-gtk25:amd64 41.1-1build1 amd64tool to take pictures and videos from your webcam - widgets ii libcheese8:amd64 41.1-1build1 amd64tool to take pictures and videos from your webcam - base library ii libclutter-gtk-1.0-0:amd64 1.8.4-4build2 amd64Open GL based interactive canvas library GTK+ widget ii libcolord-gtk1:amd64 0.3.0-1 amd64GTK+ convenience library for interacting with colord ii libdbusmenu-gtk3-4:amd64 16.04.1+18.10.20180917-0ubuntu8 amd64library for passing menus over DBus - GTK+ version ii libgtk-3-0:amd64 3.24.33-1ubuntu1 amd64GTK graphical user interface library ii libgtk-3-bin 3.24.33-1ubuntu1 amd64programs for the GTK graphical
[Desktop-packages] [Bug 1968957] [NEW] Cheese displays red-green lines in 22.04
Public bug reported: [Steps to reproduce] 1. Launch cheese 1.1. $ cheese (cheese:5504): Gdk-WARNING **: 12:16:54.536: Native Windows taller than 65535 pixels are not supported Gdk-Message: 12:16:54.981: Error 71 (Protocol error) dispatching to Wayland display. 1.2. $ sudo cheese displays "red-green lines". [Expected result] Cheese app works normally. [Actual result] The cheese app doesn't work as normal on Jammy. [Additional information] 1. tried "ubuntu-bug ... cheese" and it seems display a video on cheese but same result (red-green lights). 2. I'm not able to use `ubuntu-bug` to report the bug because it shows not found ".cache/CheeseDebug.txt". I saw it under /root/. Will attach it. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy $ dpkg -l | grep "cheese\|wayland\|gtk" ii apport-gtk 2.20.11-0ubuntu81 all GTK+ frontend for the apport crash report system ii cheese 41.1-1build1 amd64tool to take pictures and videos from your webcam ii cheese-common 41.1-1build1 all Common files for the Cheese tool to take pictures and videos ii gir1.2-gtk-3.0:amd64 3.24.33-1ubuntu1 amd64GTK graphical user interface library -- gir bindings ii gir1.2-gtk-4.0:amd64 4.6.2+ds-1ubuntu2 amd64GTK graphical user interface library -- gir bindings ii gir1.2-gtksource-4:amd64 4.8.3-1 amd64gir files for the GTK+ syntax highlighting widget ii gir1.2-javascriptcoregtk-4.0:amd64 2.36.0-2ubuntu1 amd64JavaScript engine library from WebKitGTK - GObject introspection data ii gstreamer1.0-gtk3:amd641.20.1-1ubuntu1 amd64GStreamer plugin for GTK+3 ii gtk-update-icon-cache 3.24.33-1ubuntu1 amd64icon theme caching utility ii gtk2-engines-murrine:amd64 0.98.2-3build2 amd64cairo-based gtk+-2.0 theme engine ii gtk2-engines-pixbuf:amd64 2.24.33-2ubuntu2 amd64pixbuf-based theme for GTK 2 ii ibus-gtk:amd64 1.5.26-4 amd64Intelligent Input Bus - GTK2 support ii ibus-gtk3:amd641.5.26-4 amd64Intelligent Input Bus - GTK3 support ii ibus-gtk4:amd641.5.26-4 amd64Intelligent Input Bus - GTK4 support ii libavahi-ui-gtk3-0:amd64 0.8-5ubuntu5 amd64Avahi GTK+ User interface library for GTK3 ii libcanberra-gtk3-0:amd64 0.30-10ubuntu1 amd64GTK+ 3.0 helper for playing widget event sounds with libcanberra ii libcanberra-gtk3-module:amd64 0.30-10ubuntu1 amd64translates GTK3 widgets signals to event sounds ii libcheese-gtk25:amd64 41.1-1build1 amd64tool to take pictures and videos from your webcam - widgets ii libcheese8:amd64 41.1-1build1 amd64tool to take pictures and videos from your webcam - base library ii libclutter-gtk-1.0-0:amd64 1.8.4-4build2 amd64Open GL based interactive canvas library GTK+ widget ii libcolord-gtk1:amd64 0.3.0-1 amd64GTK+ convenience library for interacting with colord ii libdbusmenu-gtk3-4:amd64 16.04.1+18.10.20180917-0ubuntu8 amd64library for passing menus over DBus - GTK+ version ii libgtk-3-0:amd64 3.24.33-1ubuntu1 amd64GTK graphical user interface library ii libgtk-3-bin 3.24.33-1ubuntu1 amd64programs for the GTK graphical user interface library ii libgtk-3-common3.24.33-1ubuntu1 all common files for the GTK graphical user interface library ii libgtk-4-1:amd64 4.6.2+ds-1ubuntu2 amd64GTK graphical user interface library ii libgtk-4-bin 4.6.2+ds-1ubuntu2 amd64programs for the GTK graphical user interface library ii libgtk-4-common4.6.2+ds-1
[Desktop-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == 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 1942789] Re: On-demand and RTD3 need to be separated
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Fix Released
Status in nvidia-prime package in Ubuntu:
Fix Released
Status in nvidia-prime source package in Focal:
Fix Released
Status in nvidia-prime source package in Hirsute:
Won't Fix
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
subprocess.call(['prime-select', 'on-demand'])
except:
pass
# Create the override file for gpu-manager
with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
f.write('# File created by ubuntu-drivers\n')
```
---
[Impact]
* Ubuntu will set GPU mode to performance as default which may use more power
* User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
* According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Test Plan]
* Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU
driver. After the installation, reboot the system. Execute "prime-select query"
should get "on-demand"
* Old GPU (which supported by nvidia-390 only) will keep in performance
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
* On non-laptop machine. Can set GPU mode to on-demand
* On laptop with GPU in runtime PM support list. Set GPU mode to on-demand
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
[Where problems could occur]
* With GPU supported RTD3 not able enable runtime PM on non-laptop.
But based on the Nvidia README, this case shall not happened.
[Other Info]
Changelogs:
nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)
[ Alberto Milone ]
* prime-select:
- Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
- on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
- Use bootvga detection when last_gfx_boot
is not available.
- Don't check the current profile when setting
a profile (LP: #1946476).
- Handle BrokenPipeError (LP: #1965520).
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-prime source package in Hirsute: New Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] Information for Focal, refer to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-prime source package in Hirsute: Won't Fix Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+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 1967456] Re: Jammy didn't use nvidia driver when executing firefox
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967456 Title: Jammy didn't use nvidia driver when executing firefox Status in OEM Priority Project: New Status in firefox package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967456/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
** Tags added: jiayi oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
The related issue reported when using Xorg:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966050
--
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967450/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Daniel, In this case, do we have any ticket for nvidia to fix the GBM issue? We would like to highlight this to nVidia. -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Daniel, Thanks for sharing! If there is a patch either from salsa or PPA then I can help to verify it in my case. ** Tags added: jiayi -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Importance: High => Critical ** Tags added: jiayi 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/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: This is on my weird desktop setup, with one monitor plugged into an AMD card and one into an NVIDIA card. When using the Wayland session, by default Shell will come up on the monitor connected to the AMD card, and the second (NVIDIA) monitor will be blank. Attempting to enable the second monitor in Display Settings will immediately and reproducibly crash gnome-shell. This is trivial for me to reproduce, so if you need patches tested I can easily do so. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2 Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 09:37:51 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-11-02 (125 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Follow-up from comment#12, I can reproduce this issue on I+N (external hdmi port wires to dGPU) on DELL-Precision-7760. --- 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc27c980 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bf50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 三 31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faf74004130 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce03b87330 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55cdffba6760 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc2f7df0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc23df40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Created gbm renderer for '/dev/dri/card1' 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create gbm_surface: Operation not permitted 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: GNOME Shell crashed with signal 5 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: == Stack trace for context 0x55cdfef5c180 == 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to create fallback offscreen framebuffer: Failed to create texture 2d due to size/format constraint ... 三 31 10:57:56 ubuntu-Precision-7760 gnome-shell[5958]: Running GNOME Shell (using mutter 42.beta) as a Wayland display server --- Which also break the auto-login feature (after auto-login, gnome restart then screen back to gdm login shell) $ dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42~beta-1ubuntu2 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42~beta-1ubuntu2 amd64window manager library from the Mutter window manager ii mutter-common 42~beta-1ubuntu2 all shared files for the Mutter window manager Hi Daniel, Do you have a PPA could try your patch like this https://gitlab.gnome.org/vanvugt/mutter/-/commit/8354289650aa3ae0c531820d3a95251b627f9eb4 ? ** Changed in: oem-priority Status: New => Confirmed -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic
