Comment 19 for bug 44562

This bug's fairly far out of date and has no recent testing activity, but the original issue is probably fixed. We've implemented a new Screen Resolution tool since the last comment, which includes xrandr-based per-user resolution setting that I *think* will address the crux of the issue here.

The issue with the gdm login screen having its own resolution is a separate issue and already reported elsewhere. (Also there's nothing we can easily do about it in the near term.) gdm has changed a bit since this original report, so maybe the current behavior is more acceptable (in my testing it seems ok on some systems, but still not quite right on others, but I think it might be a missing-EDID problem.)