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 571214 - If driver doesn't support RR1.2, but another tool that supports it is available, fallback
If driver doesn't support RR1.2, but another tool that supports it is availab...
Status: RESOLVED WONTFIX
Product: gnome-control-center
Classification: Core
Component: Display
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Federico Mena Quintero
Control-Center Maintainers
Depends on:
Blocks: randr-tracker
 
 
Reported: 2009-02-10 18:20 UTC by Mario Limonciello
Modified: 2010-11-09 18:55 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement

Attachments
patch to fallback to vendor tools if they are found (6.08 KB, patch)
2009-02-10 18:23 UTC, Mario Limonciello 		none Details | Review

Description Mario Limonciello 2009-02-10 18:20:40 UTC 
I've seen some crasher bugs happening when working with the NVIDIA or AMD closed drivers.  Those drivers don't yet adhere to RR1.2, but likely will eventually.

Rather than trying to fix crasher bugs with an old RR implementation, I think it makes sense to steer people to using the tools that the vendor provides.
Comment 1 Mario Limonciello 2009-02-10 18:23:16 UTC 
Created attachment 128398 [details] [review]
patch to fallback to vendor tools if they are found
Comment 2 Federico Mena Quintero 2009-02-26 01:56:49 UTC 
Hmm, interesting approach!  I like it that you finally found a use for the driver_is_randr_1_0 check :)

Let me give this a try and I'll get back to you.
Comment 3 Mario Limonciello 2009-02-26 02:26:31 UTC 
Since posting that patch I've actually added this to Ubuntu Jaunty.  If you want to see it in action, go ahead and try one of the alphas.  I've also set the string in the glade file as translatable (it's a one line diff)
Comment 4 Bastien Nocera 2010-11-09 18:23:29 UTC 
I'd rather we fixed the crashers in the XRandR 1.0 code paths instead...
Comment 5 Mario Limonciello 2010-11-09 18:55:08 UTC 
Does that really make sense to fix them though?  I mean they could easily just be things that are aggravated by the closed drivers not fully adhering to RR1.0 as well.  All "good" drivers support RR1.2 at least now.

This patch doesn't actually cause the RR 1.0 code path to be disabled, just recommends the user against from using it.  They can still select "No" in the dialog and get GCC open and (try to) use the RR 1.0 codepath.