After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791962 - Screen goes blank three times when logging in for the first time after a reboot
Screen goes blank three times when logging in for the first time after a reboot
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-12-26 13:37 UTC by Dima Ryazanov
Modified: 2018-04-28 23:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of the color profile (43.04 KB, image/png)
2018-03-01 10:06 UTC, Dima Ryazanov
Details

Description Dima Ryazanov 2017-12-26 13:37:04 UTC
While Gnome is starting up, the screen turns off for a second, then turns back on for a couple seconds, then turns off again like that two more times. See the video here: https://www.dropbox.com/s/p43356vclygpyw6/2017-12-26%2015.02.23.mp4?dl=0

This affects every user account, not just my regular one. If I log out and then log in again (even as a different user), everything works fine; the problem occurs only the first time after a reboot. Also, it only happens in a Wayland session, not an X11 one.

It looks like it has something to do with reconfiguring the monitor rather than turning it off: if I press Super to open the app overview, it gets dismissed when the screen turns off.

I'm running Fedora 27 on a Dell Latitude E7470.
Comment 1 Dima Ryazanov 2017-12-26 13:41:10 UTC
Oh wow, just discovered something after starting the X11 session. Gnome thinks I have a second monitor attached (which I don't). I can move the mouse to the right, off the screen; window context menus have a "Move to Monitor Right" option, and "xrandr" shows the following:

$ xrandr 
Screen 0: minimum 320 x 200, current 2944 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
   1920x1080     60.02*+  47.99  
   1400x1050     59.98  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.04    60.00  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   800x600       60.00    60.32    56.25  
   700x525       59.98  
   640x512       60.02  
   640x480       60.00    59.94  
   512x384       60.00  
   400x300       60.32    56.34  
   320x240       60.05  
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
DP-1-3 connected 1024x768+1920+0 (normal left inverted right x axis y axis) 530mm x 290mm
   1024x768      60.00*+  75.03  
   1280x1024     75.02    60.02  
   800x600       75.00    60.32  
   640x480       75.00    59.94  
   720x400       70.08  


(My laptop only has two connectors, by the way: HDMI and DP.)
Comment 2 Dima Ryazanov 2017-12-26 13:52:42 UTC
The Gnome display settings are showing a non-existent monitor, Synaptics Inc 24". That led to me this bug report in Ubuntu: https://bugzilla.gnome.org/show_bug.cgi?id=791962. Surprisingly, it was reported on the same hardware, Latitude e7470.
Comment 3 Dima Ryazanov 2018-02-02 18:59:58 UTC
I've tried using an older kernel and even downgrading the BIOS - but that made no difference.

If I start Xorg on its own, the non-existent monitor does not show up. However, if I run startx (which ends up starting Gnome), the problem does happen. So it sounds like it is actually Gnome that's somehow creating a fake monitor.

Any other info I could provide?
Comment 4 Roman 2018-02-12 17:31:07 UTC
I have the same problem. Under wayland it turns three times black. With X11 sometimes it turns black once. I also see the "second" screen with xrandr.

I noticed under wayland that if an external screen is connected to my Dell e7470 it removes the screen in gnome and reattaches it. this happens everytime it turns black.

I know for sure that with the default packages (no updates installed) it is not happening, so it must be some packages. Unfortunately I cannot limit it to certain packages. I also recognized that sometime when fedora is installing packages it also turns black multiple times.

I also updated the BIOS of my laptop, but it didn't help.

The second screen under x11 is even more annoying then the black screens at the beginning in a wayland session, because some apps spawn und the second screen.
Comment 5 Roman 2018-02-14 21:22:26 UTC
today I recognized that also under the wayland session it creates a second screen. After the three black screens this one is gone.

➜  ~ xrandr
Screen 0: minimum 320 x 200, current 2944 x 1080, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     59.96*+
XWAYLAND1 connected 1024x768+1920+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      59.92*+
➜  ~ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     59.96*+
Comment 6 Dima Ryazanov 2018-03-01 09:57:53 UTC
Apparently, the fake screen shows up in Color settings, too. It's called "PnP montor Monitor". Notice the "montor" - what is that? A typo?

A Google search for "PnP montor" produces weird results mentioning a displayport splitter.
Comment 7 Dima Ryazanov 2018-03-01 10:06:07 UTC
Created attachment 369139 [details]
Screenshot of the color profile

Hopefully there's some useful information here?

(Btw, the colors in the screenshot are wrong - the selection is actually blue, not orange. No idea how it's even possible, but the irony of a color profile dialog messing up colors in the screenshot is not lost on me.)
Comment 8 Dima Ryazanov 2018-04-28 23:35:38 UTC
I've upgraded to Fedora 28, and the bug went away - so I'm closing this.