Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#67243 - [nvidia] 450.57 2 Monitors, primary monitor does not wake up after long inactivity

Attached to Project: Arch Linux
Opened by Anton (Xakep_SDK) - Thursday, 09 July 2020, 18:47 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 13 July 2020, 00:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


1. Have 2 monitors
2. Install 450.57 driver version
3. Log in
4. Lock PC
5. While in lock screen, wait enough so screens shut down
6. Move mouse
7. Observer - one of 2 monitors did not woke up. It's primary monitor for me; i did not tried to switch it
You can fix this by switching to TTY and back while not logged in back, if you log in, switching to TTY and back or trying to lock system will result in almost full graphics system lock, only mouse will work and only screen that was active before log in

I sent several bug reports to nvidia during 450.51 beta and looks like they couldn't reproduce this.

Additional info:
* package version(s)
nvidia-dkms 450.57
Linux arch 5.7.7-zen1-1-zen
kde + sddm
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 13 July 2020, 00:50 GMT
Reason for closing:  Upstream
Additional comments about closing:  Closing this. Nothing good can come out of us tracking upstream bugs like these unless there's a viable workaround we can implement on our end. We'll have to eat the food nvidia gives us. You're much better off complaining directly on their forums.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 09 July 2020, 21:29 GMT
Thanks for the report but absolutely nothing we can do about it. Report it to nvidia. They are usually pretty quick-ish to address such regressions.