Bug 1255792 - disper can't set my monitor
disper can't set my monitor
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: disper (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Mario Santagiuliana
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-21 10:51 EDT by Steven Brandt
Modified: 2016-07-19 13:36 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 13:36:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steven Brandt 2015-08-21 10:51:59 EDT
Description of problem:
I used to use commands such as "disper -e -d DP-1,VGA-0 -r 1360x768,2048x1152" to set my monitors in Fedora 19. Now when I type it I see "There is no matching crtc for the output"

I can, however, set one display at a time using "disper -s -d DP-1 -r 1360x768." However, even then something seems off about the size of the display. It's different from what I get if I go through nvidia-settings (which forces me to click through menus every time).

Also, if I first disper -s on each monitor individually, I don't get the error message. In that case, however, it only sets up the first monitor in the list.

Version-Release number of selected component (if applicable):
0.3.1

How reproducible:
Just try to use two monitors

Steps to Reproduce:
1. disper -l, to find out what monitors you have
2. disper -e -d MON-1,MON-2 -r RES-1,RES-2
3.

Actual results:
There is no matching crtc for the output

Expected results:
My monitors to be set up.

Additional info:
Comment 1 Fedora End Of Life 2016-07-19 13:36:43 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

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