Comment 5 for bug 153800

Martin, thanks for replying.

As noted in the patch I proposed, the nvidia-legacy driver doesn't use AddARGBGLXVisuals. Bug 211752's report is correct.

 For my system, using nvidia-legacy with glx,
AllowGlXWithComposite True
 and
USEEDIDFreqs True
 are the needed clauses

AllowGLXWithComposite is the option to avoid the symptoms mentioned in this bug. USEEDIDFreqs is needed to
get the legacy driver to use the full bandwidth of any attached monitor to provide higher screen resolutions.

The nologo option avoids an ugly transition with a split second of torn nvidia logo.
From research last fall, I believe AddArgbVisuals is only a long-lived typo.

Unknown options are ignored with a warning in nvidia drivers, as noted in bug 211752 and bug 138220, so
I didn't individualize screen options in my proposed patch. I see it is now much easier to do that.

I looked at the latest code with the fix for 211752 and it looked like it wouldn't break anything. Then
I tested it today. Though I had to patch for new bug 215027, it then worked fine with my video card.

I see that displayconfig-gtk is gone or hidden. If it is permanently gone is it time to close this bug with no action?

In any case I'd like to help out by testing anything you need with my old (I mean legacy) video card. Please
let me know if I can be of any assistance.