We could MIR libdisplay-info, it seems to have practically no dependencies. But on the other hand, the amount of code in Mutter that actually depends on "HAVE_LIBDISPLAY_INFO" is quite small. It could be replicated inline within Mutter, though I doubt upstream would want to.
Tracing the field relevant to this bug through the Mutter code (meta_monitor_get_min_refresh_rate), it doesn't look like it has any real function other than a cosmetic one in returning the minimum refresh rate over D-Bus back to the Settings app. Perhaps it should be used in future if that helps to prevent bug 2066080, but for now this bug seems to be purely cosmetic and unimportant. ** Changed in: mutter (Ubuntu) Importance: Medium => Low ** Tags added: oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063147 Title: No lower VRR range for display shown in Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063147/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
