There's no way to "fix" this bug until openchrome grows dual head support. Currently, there's no way to have a different resolution and refresh rate on different output, the lower one will apply to both output. See comment #4.
Hopefully, dual head support shouldn't be too far away, I'll make sure to update both the rawhide package and the F10 testing package as soon as it enters upstream.
There's no way to "fix" this bug until openchrome grows dual head support. Currently, there's no way to have a different resolution and refresh rate on different output, the lower one will apply to both output. See comment #4.
Hopefully, dual head support shouldn't be too far away, I'll make sure to update both the rawhide package and the F10 testing package as soon as it enters upstream.