Comment 36 for bug 2020782
Revision history for this message
| Fabio Augusto Miranda Martins (fabio.martins) wrote | #36 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
Daniel,
A few items to make sure I'm on the same page:
1. So, IIUC, you're saying that the "final fix" should be the vv5 package, which contains the fix to the zero hz bug (loosening mutter to accept zero-Hz, as this is the bogus refresh rate being reported by Xdcv) + the caveat for AWS to either fix Xdcv or never try to enable Fractional scaling in the instance (details in your comment#16), is that so?
2. Regarding your comment on bug 1857392 and bug 2007742 being present, iiuc they do not have a noticeable impact (other than spamming the log).
3. Also, I need to mention that I went ahead and tried once more the vv5 package on a AWS Workspace, and I can no longer reproduce the blank screen. Now I see these logs [1] and the scale does get reverted from 200% to 100%.
https:/
4. If 1 above is correct, then where (if anywhere) we are going to investigate the situation where vv5 causes the other monitors to get automatically enabled?
Regards,
Fabio Martins