| 2019-09-16 12:11:15 |
Alberto Milone |
bug |
|
|
added bug |
| 2019-09-16 12:11:54 |
Alberto Milone |
bug task added |
|
nvidia-graphics-drivers-435 (Ubuntu) |
|
| 2019-09-16 12:12:36 |
Alberto Milone |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-09-16 12:12:36 |
Alberto Milone |
bug task added |
|
nvidia-graphics-drivers-430 (Ubuntu Bionic) |
|
| 2019-09-16 12:12:36 |
Alberto Milone |
bug task added |
|
nvidia-graphics-drivers-435 (Ubuntu Bionic) |
|
| 2019-09-16 12:12:46 |
Alberto Milone |
nvidia-graphics-drivers-430 (Ubuntu): status |
New |
Fix Released |
|
| 2019-09-16 12:12:50 |
Alberto Milone |
nvidia-graphics-drivers-430 (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-09-16 12:12:53 |
Alberto Milone |
nvidia-graphics-drivers-435 (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-09-16 12:13:04 |
Alberto Milone |
nvidia-graphics-drivers-435 (Ubuntu): status |
New |
Fix Released |
|
| 2019-09-16 12:13:11 |
Alberto Milone |
nvidia-graphics-drivers-430 (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-09-16 12:13:15 |
Alberto Milone |
nvidia-graphics-drivers-435 (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-09-16 12:13:19 |
Alberto Milone |
nvidia-graphics-drivers-430 (Ubuntu Bionic): assignee |
|
Alberto Milone (albertomilone) |
|
| 2019-09-16 12:13:22 |
Alberto Milone |
nvidia-graphics-drivers-435 (Ubuntu Bionic): assignee |
|
Alberto Milone (albertomilone) |
|
| 2019-09-16 13:01:20 |
Alberto Milone |
description |
Update NVIDIA the 430 series and introduce the 435 series from 19.10. |
Update NVIDIA the 430 series and introduce the 435 series from 19.10.
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
<TODO Document any QA done, automated and manual>
The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
<TODO: attach nvidia-proposed test artifacts for every SRU release, not a link as links expire>
[Discussion]
430.50:
* New upstream release (LP: #1844126):
- Fixed display color range handling on pre-Turing GPUs, such
that when limited color range is selected through the display
controls page in nvidia-settings, output pixel values will be
correctly clamped to Consumer Technology Association (CTA)
range.
435.21:
* New upstream release:
- Fixed a bug that caused the X server to crash when using
HardDPMS with an NVIDIA-driven GPU Screen.
- Fixed a bug which caused the kernel to panic when exiting a
single X server when multiple X servers were active and in an
SLI configuration.
- Fixed a regression introduced in the 430.* series of releases
that caused a segmentation fault in libnvcuvid.so while using
Video Codec SDK APIs on certain graphics boards.
- Added initial experimental support for runtime D3 (RTD3) power
management on Turing notebook GPUs.
- Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
power management information.
- Improved nvidia-bug-report.sh to collect ACPI tables when the
acpidump tool is available.
- Added Vulkan and OpenGL+GLX support for PRIME render offload.
Please see the PRIME Render Offload chapter in the README for
system requirements and configuration details.
- Added support for changing Digital Vibrance in the display
controls section of nvidia-settings on Turing hardware.
- Fixed the cuvidParseVideoData API in the NVCUVID driver to
correctly propagate errors returned by the
PFNVIDSEQUENCECALLBACK callback function to the application.
- Fixed a bug that caused the NVIDIA X driver to behave
incorrectly or crash when a client queried Xinerama information
on X servers with a non-NVIDIA X screen as screen 0.
- Fixed the "Image Settings" options in the "OpenGL Settings"
page of nvidia-settings for Quadro GPUs. Previously, OpenGL
rendering on Quadro would behave as if the "High Quality"
option were selected regardless of the selection. Now, the
setting will default to "High Quality" for Quadro but selecting
a lower option will affect rendering accordingly. (Other GPUs
are unchanged: the default remains "Quality", but other options
can be selected if desired.)
- Fixed a bug that could cause Vulkan applications to generate
spurious warning messages about a missing NV-GLX extension.
- Fixed a bug that prevented nvidia-drm from marking preferred
modes properly when reporting display information via the DRM-
KMS API.
- Fixed the NvEncodeAPI driver to correctly reject the encoding
of sequences with resolutions smaller than what the NVENC
supports.
- Fixed display color range handling on pre-Turing GPUs, such
that when limited color range is selected through the display
controls page in nvidia-settings, output pixel values will be
correctly clamped to Consumer Technology Association (CTA)
range. |
|
| 2019-09-16 13:26:52 |
Alberto Milone |
description |
Update NVIDIA the 430 series and introduce the 435 series from 19.10.
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
<TODO Document any QA done, automated and manual>
The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
<TODO: attach nvidia-proposed test artifacts for every SRU release, not a link as links expire>
[Discussion]
430.50:
* New upstream release (LP: #1844126):
- Fixed display color range handling on pre-Turing GPUs, such
that when limited color range is selected through the display
controls page in nvidia-settings, output pixel values will be
correctly clamped to Consumer Technology Association (CTA)
range.
435.21:
* New upstream release:
- Fixed a bug that caused the X server to crash when using
HardDPMS with an NVIDIA-driven GPU Screen.
- Fixed a bug which caused the kernel to panic when exiting a
single X server when multiple X servers were active and in an
SLI configuration.
- Fixed a regression introduced in the 430.* series of releases
that caused a segmentation fault in libnvcuvid.so while using
Video Codec SDK APIs on certain graphics boards.
- Added initial experimental support for runtime D3 (RTD3) power
management on Turing notebook GPUs.
- Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
power management information.
- Improved nvidia-bug-report.sh to collect ACPI tables when the
acpidump tool is available.
- Added Vulkan and OpenGL+GLX support for PRIME render offload.
Please see the PRIME Render Offload chapter in the README for
system requirements and configuration details.
- Added support for changing Digital Vibrance in the display
controls section of nvidia-settings on Turing hardware.
- Fixed the cuvidParseVideoData API in the NVCUVID driver to
correctly propagate errors returned by the
PFNVIDSEQUENCECALLBACK callback function to the application.
- Fixed a bug that caused the NVIDIA X driver to behave
incorrectly or crash when a client queried Xinerama information
on X servers with a non-NVIDIA X screen as screen 0.
- Fixed the "Image Settings" options in the "OpenGL Settings"
page of nvidia-settings for Quadro GPUs. Previously, OpenGL
rendering on Quadro would behave as if the "High Quality"
option were selected regardless of the selection. Now, the
setting will default to "High Quality" for Quadro but selecting
a lower option will affect rendering accordingly. (Other GPUs
are unchanged: the default remains "Quality", but other options
can be selected if desired.)
- Fixed a bug that could cause Vulkan applications to generate
spurious warning messages about a missing NV-GLX extension.
- Fixed a bug that prevented nvidia-drm from marking preferred
modes properly when reporting display information via the DRM-
KMS API.
- Fixed the NvEncodeAPI driver to correctly reject the encoding
of sequences with resolutions smaller than what the NVENC
supports.
- Fixed display color range handling on pre-Turing GPUs, such
that when limited color range is selected through the display
controls page in nvidia-settings, output pixel values will be
correctly clamped to Consumer Technology Association (CTA)
range. |
Update NVIDIA the 430 series and introduce the 435 series from 19.10.
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
430.50:
* New upstream release (LP: #1844126):
- Fixed display color range handling on pre-Turing GPUs, such
that when limited color range is selected through the display
controls page in nvidia-settings, output pixel values will be
correctly clamped to Consumer Technology Association (CTA)
range.
435.21:
* New upstream release:
- Fixed a bug that caused the X server to crash when using
HardDPMS with an NVIDIA-driven GPU Screen.
- Fixed a bug which caused the kernel to panic when exiting a
single X server when multiple X servers were active and in an
SLI configuration.
- Fixed a regression introduced in the 430.* series of releases
that caused a segmentation fault in libnvcuvid.so while using
Video Codec SDK APIs on certain graphics boards.
- Added initial experimental support for runtime D3 (RTD3) power
management on Turing notebook GPUs.
- Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
power management information.
- Improved nvidia-bug-report.sh to collect ACPI tables when the
acpidump tool is available.
- Added Vulkan and OpenGL+GLX support for PRIME render offload.
Please see the PRIME Render Offload chapter in the README for
system requirements and configuration details.
- Added support for changing Digital Vibrance in the display
controls section of nvidia-settings on Turing hardware.
- Fixed the cuvidParseVideoData API in the NVCUVID driver to
correctly propagate errors returned by the
PFNVIDSEQUENCECALLBACK callback function to the application.
- Fixed a bug that caused the NVIDIA X driver to behave
incorrectly or crash when a client queried Xinerama information
on X servers with a non-NVIDIA X screen as screen 0.
- Fixed the "Image Settings" options in the "OpenGL Settings"
page of nvidia-settings for Quadro GPUs. Previously, OpenGL
rendering on Quadro would behave as if the "High Quality"
option were selected regardless of the selection. Now, the
setting will default to "High Quality" for Quadro but selecting
a lower option will affect rendering accordingly. (Other GPUs
are unchanged: the default remains "Quality", but other options
can be selected if desired.)
- Fixed a bug that could cause Vulkan applications to generate
spurious warning messages about a missing NV-GLX extension.
- Fixed a bug that prevented nvidia-drm from marking preferred
modes properly when reporting display information via the DRM-
KMS API.
- Fixed the NvEncodeAPI driver to correctly reject the encoding
of sequences with resolutions smaller than what the NVENC
supports.
- Fixed display color range handling on pre-Turing GPUs, such
that when limited color range is selected through the display
controls page in nvidia-settings, output pixel values will be
correctly clamped to Consumer Technology Association (CTA)
range. |
|
| 2019-09-16 13:38:55 |
Steve Langasek |
nvidia-graphics-drivers-430 (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-09-16 13:38:57 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-09-16 13:39:00 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2019-09-16 13:39:02 |
Steve Langasek |
tags |
|
verification-needed verification-needed-bionic |
|
| 2019-09-23 15:56:32 |
Graham Inggs |
bug task added |
|
nvidia-settings (Ubuntu) |
|
| 2019-09-24 10:22:41 |
Alberto Milone |
nvidia-settings (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-09-24 10:22:46 |
Alberto Milone |
nvidia-settings (Ubuntu): status |
New |
Fix Released |
|
| 2019-11-07 14:22:58 |
Alberto Milone |
tags |
verification-needed verification-needed-bionic |
verification-done-bionic verification-needed |
|
| 2019-11-07 14:23:08 |
Alberto Milone |
tags |
verification-done-bionic verification-needed |
verification-done verification-done-bionic |
|
| 2019-11-07 14:31:58 |
Launchpad Janitor |
nvidia-graphics-drivers-435 (Ubuntu Bionic): status |
In Progress |
Fix Released |
|
| 2019-11-07 14:33:59 |
Timo Aaltonen |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-11-07 14:34:36 |
Launchpad Janitor |
nvidia-graphics-drivers-430 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
