Bug 1040062

Summary:	gnome-control-center display cannot get screen information
Product:	[Fedora] Fedora	Reporter:	W. Michael Petullo <mike>
Component:	control-center	Assignee:	Control Center Maintainer <control-center-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	bzrh.bobd, ckozler, control-center-maint, fmuellner, leho, mkasik, ofourdan, pbabinca, peter.meier, rabin, rmatos, rstrode, tiagomatos
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-13 12:57:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description W. Michael Petullo 2013-12-10 16:05:55 UTC

Description of problem:
When I run "gnome-control-center display" the tool prints only "Could not get screen information". I am using an old MacBook, and lspci identifies its graphics chipset as "02:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9400M] (rev b1)".

Version-Release number of selected component (if applicable):
control-center-3.10.2-3.fc20.x86_64
xorg-x11-drv-nouveau-1.0.9-2.fc20.x86_64

How reproducible:
Every time

Steps to Reproduce:
Run "gnome-control-center display".

Actual results:
Note the message: "Could not get screen information". (This happens whether or not I have my second display connected to my laptop.)

Expected results:
I should be able to manipulate my screen and second display.

Additional info:
xrandr reports:

Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 8192 x 8192
LVDS-1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 286mm x 178mm
   1280x800       61.2*+
   1024x768       60.8  
   800x600        60.6  
   640x480        60.6  
   720x400        60.9  
   640x400        60.7  
   640x350        60.6  
DP-1 connected 1920x1200+1280+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200      60.0*+
   1600x1200      60.0  
   1280x1024      75.0     60.0  
   1152x864       75.0  
   1024x768       75.1     60.0  
   800x600        75.0     60.3  
   640x480        75.0     60.0  
   720x400        70.1

Comment 1 Peter Meier 2014-01-23 11:17:50 UTC

I'm having the same issue since upgrading to F20:

$  xrandr 
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
LVDS1 connected (normal left inverted right x axis y axis)
   1366x768       60.0 +
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        59.9  
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200      60.0*+
   1600x1200      60.0  
   1680x1050      59.9  
   1280x1024      75.0     60.0  
   1440x900       59.9  
   1280x800       59.9  
   1152x864       75.0  
   1152x720       60.0  
   1024x768       75.1     60.0  
   832x624        74.6  
   800x600        75.0     60.3  
   640x480        75.0     60.0  
   720x400        70.1  
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)

$ rpm -qa | grep control-center-3
control-center-3.10.2-4.fc20.x86_64

Comment 2 W. Michael Petullo 2014-03-04 01:08:33 UTC

From what I can tell by looking at things using gdb:

1. cc_display_panel_init calls gnome_rr_screen_new with screen set to non NULL.

2. Later, gnome_rr_screen_new sets rr_screen = g_object_get_data (G_OBJECT (screen), "GnomeRRScreen").

3. rr_screen is now NULL.

4. Later, gnome_rr_screen_new sets rr_screen = g_initable_new (GNOME_TYPE_RR_SCREEN, NULL, error, "gdk-screen", screen, NULL).

5. rr_screen remains NULL.

6. But now error->message is "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Mutter.DisplayConfig was not provided by any .service files".

So it seems it would help if cc_display_panel_init printed its error message based on the above string (6). Does the error string in (6) mean gnome-control-center is compatible only with GNOME panel/Metacity Clutter? I am using awesome as my window manager.

Comment 3 Leho Kraav 2014-06-08 10:46:55 UTC

I think I'm also facing this with i3wm

Comment 4 Charles Kozler 2014-11-13 12:33:09 UTC

As well with awesome wm

Comment 5 Rui Matos 2014-11-13 12:57:05 UTC

gnome-control-center's display configuration depends on the DBus service org.gnome.Mutter.DisplayConfig which is implemented by mutter. If you are not running mutter then you can't use g-c-c's display configuration.