First is, if i remove "quiet splash" from boot, the bug disappears as well.
More importantly though, if I have the blank login screen, and I connect an external monitor, the screen shows up.
If I go to a tty (Alt-Ctrl-F1) and back to X (Alt-Ctrl-F7), the screen is blank again.
Then, if I pull out the external monitor, the login screen shows up again.
Summed up
1. toggling external screen connection brings login screen up
2. switching to text and back to X kills it
It takes 1 to 2 seconds to bring the screen up after the cable is connected/disconnected.
I am on toshiba portege Z930-14L
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
By the way, I noticed (very rarely) that when logged in, the "screen refresh" may "lag", that is when for example typing a command in the shell the last character of the command would show up only after pressing enter. I believe this was not particular to the shell, but since it happend only once or twice on this new laptop I cannot tell for sure.
I might have some news for this bug:
First is, if i remove "quiet splash" from boot, the bug disappears as well.
More importantly though, if I have the blank login screen, and I connect an external monitor, the screen shows up.
If I go to a tty (Alt-Ctrl-F1) and back to X (Alt-Ctrl-F7), the screen is blank again.
Then, if I pull out the external monitor, the login screen shows up again.
Summed up
1. toggling external screen connection brings login screen up
2. switching to text and back to X kills it
It takes 1 to 2 seconds to bring the screen up after the cable is connected/ disconnected.
I am on toshiba portege Z930-14L
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
By the way, I noticed (very rarely) that when logged in, the "screen refresh" may "lag", that is when for example typing a command in the shell the last character of the command would show up only after pressing enter. I believe this was not particular to the shell, but since it happend only once or twice on this new laptop I cannot tell for sure.
Can I do anything to further debug this?
BR, Chris