Bug 922596 - mate-control-center does not detect monitor type and does not set appropriate resolution
Summary: mate-control-center does not detect monitor type and does not set appropriate...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-control-center
Version: 18
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/mate-desktop/mate-...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-18 03:27 UTC by pgaltieri
Modified: 2013-05-24 05:25 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-24 05:25:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screen shot of mate-display-properties showing unknown monitor type (18.14 KB, image/png)
2013-03-18 03:27 UTC, pgaltieri
no flags Details

Description pgaltieri 2013-03-18 03:27:09 UTC
Created attachment 711709 [details]
Screen shot of mate-display-properties showing unknown monitor type

Description of problem:
Mate control center does not detect my monitor.  It shows the monitor as unknown and sets the screen resolution to 1280x1024 rather than the 1920x1200.

I have a kvm switch.  Attached to that switch are 3 systems, 1 running F14, one running F16 and one running F18.  The monitor is detected and configured correctly on all the systems except the F18 system.

Version-Release number of selected component (if applicable):
Version 1.5.4-1.fc18 of mate-control-center.i686

The monitor I have is a Gateway FPD2485W.

How reproducible:
Always.

Steps to Reproduce:
1. Start up the mate-control-center
2. Select Monitors
3. Click on Detect monitors
  
Actual results:
Displays Unknown for monitor type, sets resolution to 1280x1024 and refresh rate to 0hz


Expected results:
It should display the monitor type, Gateway 2000 24" (this is what it displays on F14), a resolution of 1920x1200 and a refresh rate of 60hz

Additional info:
The KVM is an iogear GCS634U. I have attached a screenshot.

The system has all the latest updates and I have rebooted it several times and I have never gotten to monitor to configure correctly.

Comment 1 Dan Mashal 2013-03-19 05:09:12 UTC
Have you tried this with a different DE?

Comment 2 pgaltieri 2013-03-19 18:20:32 UTC
I tried it with Gnome 3.  It labels the monitor as laptop, and sets the screen resolution to 1280x1024 with normal rotation.  It does not show a refresh rate at all.

Comment 3 Dan Mashal 2013-03-19 19:47:26 UTC
Thanks.

Comment 4 Dan Mashal 2013-03-19 19:59:14 UTC
Please use the following workaround for now:

xrandr --display VGA1 --auto --primary

replacing VGA1 for xrandr's name of your second monitor, then click "Make Default", it will return to that configuration when you plug the secondary monitor back in.

At least, so far it seems to.

Comment 5 pgaltieri 2013-03-19 20:31:39 UTC
On the F18 system running xrandr with no options produces:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
   1280x1024       0.0* 
   1024x768        0.0  
   800x600         0.0  
   640x480         0.0  

On F14 xrandr with no options produces:

Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
DVI-I-1 disconnected (normal left inverted right x axis y axis)
VGA-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200      59.9*+
   1600x1200      60.0  
   1680x1050      74.9     60.0  
   1400x1050      60.0  
   1280x1024      75.0     60.0  
   1440x900       75.0     59.9  
   1152x864       75.0  
   1024x768       75.1     70.1     60.0  
   800x600        72.2     75.0     60.3     56.2  
   640x480        72.8     75.0     60.0  
   720x400        70.1  

On F16 xrandr with no options produces:

Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 4096 x 4096
LVDS-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1680x1050      60.0*+   60.0  
   1400x1050      60.0  
   1280x1024      59.9  
   1280x960       59.9  
   1152x864       60.0  
   1024x768       59.9  
   800x600        59.9  
   640x480        59.4  
   720x400        59.6  
   640x400        60.0  
   640x350        59.8  
VGA-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200      59.9*+
   1920x1080      60.0  
   1600x1200      65.0     60.0  
   1680x1050      74.9     60.0  
   1680x945       60.0  
   1400x1050      74.9     60.0  
   1600x900       60.0  
   1280x1024      75.0     60.0  
   1440x900       75.0     59.9  
   1280x960       60.0  
   1366x768       60.0  
   1360x768       60.0  
   1280x800       74.9     59.8  
   1152x864       75.0  
   1280x768       74.9     59.9  
   1024x768       75.1     70.1     60.0  
   1024x576       60.0  
   800x600        72.2     75.0     60.3     56.2  
   848x480        60.0  
   640x480        72.8     75.0     60.0  
   720x400        70.1  
DVI-I-1 disconnected (normal left inverted right x axis y axis)
TV-1 disconnected (normal left inverted right x axis y axis)

Note that the F16 system is a laptop.

On the F18 system I only have one monitor attached the same as on the F14 system.  Only the F16 system has 2 monitors, one the laptop screen the other the Gateway external monitor.

It's also interesting to note that F14 shows a maximum of 8192x8192 while F16 show a maximum of 4096x4096.

Given this info F18 still fails to determine the correct resolution of the monitor.

Also the command you provided doesn't work

xrandr --display VGA1 --auto --primary
xrandr: unrecognized option '--display'
Try 'xrandr --help' for more information.

I tried:

xrandr --dryrun -display VGA1 --output --auto --primary
Can't open display VGA1

Which is true since no VGA1 display is found.

Comment 6 Fedora Admin XMLRPC Client 2013-04-03 14:22:56 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Dan Mashal 2013-04-12 06:16:39 UTC
Are you still experiencing issues? Currently this is working fine for me. Please see attached screenshot.

Comment 8 pgaltieri 2013-04-12 16:31:38 UTC
When I go to System->Preferences->Monitors it still shows monitor as unknown and xrandr still outputs the following:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
   1280x1024       0.0* 
   1024x768        0.0  
   800x600         0.0  
   640x480         0.0 

Until xrandr displays something similar to the following:

Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 4096 x 4096
LVDS-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1680x1050      60.0*+   60.0  
   1400x1050      60.0  
   1280x1024      59.9  
   1280x960       59.9  
   1152x864       60.0  
   1024x768       59.9  
   800x600        59.9  
   640x480        59.4  
   720x400        59.6  
   640x400        60.0  
   640x350        59.8  
VGA-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200      59.9*+
   1920x1080      60.0  
   1600x1200      65.0     60.0  
   1680x1050      74.9     60.0  
   1680x945       60.0  
   1400x1050      74.9     60.0  
   1600x900       60.0  
   1280x1024      75.0     60.0  
   1440x900       75.0     59.9  
   1280x960       60.0  
   1366x768       60.0  
   1360x768       60.0  
   1280x800       74.9     59.8  
   1152x864       75.0  
   1280x768       74.9     59.9  
   1024x768       75.1     70.1     60.0  
   1024x576       60.0  
   800x600        72.2     75.0     60.3     56.2  
   848x480        60.0  
   640x480        72.8     75.0     60.0  
   720x400        70.1  
DVI-I-1 disconnected (normal left inverted right x axis y axis)
TV-1 disconnected (normal left inverted right x axis y axis)

The VGA output above is for the same monitor, but attached to a system running F16.

Comment 9 Dan Mashal 2013-05-24 05:25:47 UTC
I'm going to blame your video card drivers and the kernel on this. I can't do anything about this.


Note You need to log in before you can comment on or make changes to this bug.