FS#50057 - [nvidia] startx and blank screen with latest nvidia drivers
Attached to Project:
Arch Linux
Opened by Ebrahim Azarisooreh (eazar001) - Friday, 15 July 2016, 23:41 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 15 August 2016, 20:49 GMT
Opened by Ebrahim Azarisooreh (eazar001) - Friday, 15 July 2016, 23:41 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 15 August 2016, 20:49 GMT
|
Details
Description:
With this latest release of the NVIDIA drivers, Arch Linux boots up and loads `startx` with a black screen. I'm currently using xmonad wm, but can also reproduce this issue with jwm as well. Additional info: * NVIDIA version 367.35-1 * Xmonad 0.12 NOTE: When I try to login to tty2 with CTRL+ALT+F2, and then go back to the session with the blank screen (tty1) by doing CTRL+ALT+F1 afterwards, I'm able to see my Xmonad desktop. So clearly the WM started up correctly in the background, it just wasn't visible. I've only received this issue with this vsn 367.35-1 Steps to reproduce: 1) Install nvidia driver 367.35-1 2) reboot arch linux 3) see blank screen after startx is executed (i.e. from ~/.xinitrc) |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 15 August 2016, 20:49 GMT
Reason for closing: Upstream
Monday, 15 August 2016, 20:49 GMT
Reason for closing: Upstream
Comment by
Ebrahim Azarisooreh (eazar001) -
Friday, 15 July 2016, 23:44 GMT
Comment by Darek (blablo) -
Saturday, 16 July 2016, 06:50 GMT
Comment by
Ebrahim Azarisooreh (eazar001) -
Saturday, 16 July 2016, 06:57 GMT
Comment by
Sven-Hendrik Haase (Svenstaro) -
Monday, 15 August 2016, 20:49 GMT
Sorry, I forgot to enter bug report summary. `startx and blank
screen with latest nvidia drivers` should be sufficient.
https://devtalk.nvidia.com/default/topic/950647/linux/black-screen-with-367-35/
Ah okay, great so something really does appear to be wrong with
these latest drivers. I'll keep my nvidia drivers downgraded until
the next release then. Thanks for post!
Well, no point tracking an upstream bug that we can't fix really.
Closing unless there is a workaround. Please reopen in that case.