Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#60317 - [nvidia]DP can't sleep monitor
Attached to Project:
Arch Linux
Opened by Taz (Tazmain) - Friday, 05 October 2018, 15:51 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 15 December 2019, 16:41 GMT
Opened by Taz (Tazmain) - Friday, 05 October 2018, 15:51 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 15 December 2019, 16:41 GMT
|
DetailsDescription:
When using a Display port cable to a display port input on a monitor, when using 'xset dpms force off' all monitors turn off. So HMDI-HDMI screen, DP->hdmi screen, and DP-DP screen. However after 10 seconds the DP-DP screen turns on again, the backlit turns on with and appears to be grayish. It doesn't turn off at like the other screen. The DP-DP when using dual link DVI it does turn off, and with HDMI. Tried with a GTX980 card, and RTX2080 card. Same issue. Additional info: version 401.57 and 396 |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Sunday, 15 December 2019, 16:41 GMT
Reason for closing: Works for me
Additional comments about closing: Can't reproduce and also it's very unlikely that we can fix this at a packaging level. If the issue remains, please contact NVIDIA directly.
Sunday, 15 December 2019, 16:41 GMT
Reason for closing: Works for me
Additional comments about closing: Can't reproduce and also it's very unlikely that we can fix this at a packaging level. If the issue remains, please contact NVIDIA directly.
Comment by Andreas Radke (AndyRTR) -
Tuesday, 10 December 2019, 11:32 GMT
Is this still an issue?