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 696010 - Second head has no background after mutter commit 0bb8d29
Second head has no background after mutter commit 0bb8d29
Status: RESOLVED DUPLICATE of bug 696089
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-03-17 20:40 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2013-03-18 21:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joanmarie Diggs (IRC: joanie) 2013-03-17 20:40:21 UTC
Environment:
* Fedora 18
* full jhbuild environment with packages from master
* Graphics: Gallium 0.4 on NV96
* Dual head, single video card, desktop system

With gnome-shell master, clutter master, and mutter master, only the main head has my chosen background; the other head is solid grey.

I tried earlier revisions of gnome-shell and worked my way before Jasper's background fixes and still saw the problem.

I then tried gnome-shell master with mutter revision 1f905bd (i.e. the one before 0bb8d29) and both heads had backgrounds as expected. Something about 0bb8d29 is making the second head's background go away.

Other observations which may or may not be relevant:

* Each time I do the Alt+f2, r to restart gnome-shell, for a brief moment both heads have the default background. But then my background is restored and the second head goes grey.

* When using mutter revision 1f905bd, there's a noticeable delay (a full second) in between the first head getting its background and the second head getting its background.
Comment 1 Ray Strode [halfline] 2013-03-18 21:20:05 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 2 Ray Strode [halfline] 2013-03-18 21:21:20 UTC
woops, wrong canned response. Let's try this again (and thanks Joanie for going the extra mile in debugging here):

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 696089 ***