GNOME Bugzilla – Bug 741683
Monitors left half blank or garbage when applying RandR settings at login
Last modified: 2015-01-27 22:39:24 UTC
Since upgrading to Fedora Rawhide (F22) on my desktop, with gnome-settings-daemon-3.15.1-1.fc22.x86_64 , whenever I log into GNOME, my screens are both only half-initialized. The top half of each screen displays what it should, the bottom half is blank or garbage. This doesn't happen when logging into Xfce, hence I'm blaming GNOME. Running 'xrandr --output DVI-I-1 --right-of DVI-I-2' from a console seems to be enough to kick things back into shape. I have dual 22" monitors configured to display side-by-side at 1080x1920 resolution, rotated (portrait orientation). Attaching journal output from an affected boot. I log in around 13:03, and run the xrandr command manually around 13:08. Also attaching a photo.
Created attachment 292938 [details] journal
Created attachment 292939 [details] photo of the issue
(In reply to comment #0) > Since upgrading to Fedora Rawhide (F22) on my desktop, with > gnome-settings-daemon-3.15.1-1.fc22.x86_64 , whenever I log into GNOME, my > screens are both only half-initialized. The top half of each screen displays > what it should, the bottom half is blank or garbage. > > This doesn't happen when logging into Xfce, hence I'm blaming GNOME. XFCE doesn't use any compositing, nor does it use OpenGL, does it? Likely corruption caused by a bug in the gnome-shell stack, or the graphics driver. Could you please give some details about your graphics card on this system?
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) No, Xfce doesn't use compositing or OpenGL (AFAIK). But it's hard to describe but somehow it just doesn't 'feel' like a GL bug? I'll see if I can video the boot sequence later to give you an idea.
I think this may somehow have been caused by a Fedora bug which prevented g-s-d startup completing for some time - https://bugzilla.redhat.com/show_bug.cgi?id=1184453 . At least, when I installed the cups update to fix that and rebooted, I noticed this didn't happen any more. Closing for now, will re-open if it comes back.