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 597682 - Incorrect xrandr error notification when changing monitor setup CancelOk
Incorrect xrandr error notification when changing monitor setup CancelOk
Status: RESOLVED DUPLICATE of bug 610482
Product: gnome-settings-daemon
Classification: Core
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks: randr-tracker
 
 
Reported: 2009-10-07 12:59 UTC by Chris Jones
Modified: 2010-10-13 17:41 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot snippet showing the unnecessary error (32.55 KB, image/png)
2009-10-07 12:59 UTC, Chris Jones 		Details

Description Chris Jones 2009-10-07 12:59:09 UTC 
Created attachment 144953 [details]
screenshot snippet showing the unnecessary error

Reported at:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/444609

I have a laptop (Thinkpad X301) which I connect to an external monitor in some
locations, and poke Fn-F7 on it to make it notice the new display
configuration. It has an Intel X4500MHD graphics chip, and two external display
connectors - VGA and DisplayPort.

With either VGA or DisplayPort, the Fn-F7 action triggers exactly correct setup
for the displays, it will extend my desktop onto the second monitor with the
correct resolution and frequency.
This is, obviously, fantastic.

For some reason it then displays an error notification saying "could not set
the configuration for CRTC 58" (or 57 in the case of VGA).

Presumably the error is necessary in some circumstances, but it seems redundant
in mine, since everything seems to work fine after pressing the button.
Comment 1 Bastien Nocera 2010-10-13 17:41:45 UTC 
I believe this is a duplicate of bug 610482. If the problem still happens with GNOME 2.30 or later, please reopen this bug.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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