We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems an xserver bug.
Although only tested under xgb and xpyb, but xserver didn't send the rates field of GetScreenInfoReply.
This will cause panic.
I have report it to https://bugs.freedesktop.org/show_bug.cgi?id=73180
The text was updated successfully, but these errors were encountered:
I'm seeing something similar with an out of bounds slice access in randr.RefreshRatesRead. This diff hides the problem for me:
randr.RefreshRatesRead
diff --git i/randr/randr.go w/randr/randr.go index 20dc62a..d0e35ac 100644 --- i/randr/randr.go +++ w/randr/randr.go @@ -1299,6 +1299,9 @@ type RefreshRates struct { // RefreshRatesRead reads a byte slice into a RefreshRates value. func RefreshRatesRead(buf []byte, v *RefreshRates) int { + if len(buf) == 0 { + return 0 + } b := 0 v.NRates = xgb.Get16(buf[b:])
Sorry, something went wrong.
No branches or pull requests
It seems an xserver bug.
Although only tested under xgb and xpyb, but xserver didn't send the rates field of GetScreenInfoReply.
This will cause panic.
I have report it to https://bugs.freedesktop.org/show_bug.cgi?id=73180
The text was updated successfully, but these errors were encountered: