Bug 73180 - randr getscreeninfo malformed packget
Summary: randr getscreeninfo malformed packget
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/XrandR (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Keith Packard
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-31 04:41 UTC by snyh
Modified: 2018-08-10 20:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
the wireshark caputred packet when run above python code (17.91 KB, text/plain)
2013-12-31 04:41 UTC, snyh
no flags Details

Description snyh 2013-12-31 04:41:38 UTC
Created attachment 91355 [details]
the wireshark caputred packet when run above python code

import xcb
from xcb import randr

con = xcb.connect()

ran = con(randr.key)
ver = ran.QueryVersion(1, 3).reply()

root = con.get_setup().roots[0].root

ran.GetScreenInfo(root).reply()


this will panic:
Traceback (most recent call last):
  File "a.py", line 11, in <module>
    ran.GetScreenInfo(root).reply()
  File "/usr/lib/python2.7/dist-packages/xcb/randr.py", line 101, in __init__
    self.rates = xcb.List(parent, offset, (self.nInfo - self.nSizes), RefreshRates, -1)
  File "/usr/lib/python2.7/dist-packages/xcb/randr.py", line 56, in __init__
    (self.nRates,) = unpack_from('H', parent, offset)
struct.error: unpack_from requires a buffer of at least 2 bytes


because the xserver reply an malformed package, seems caused by this commit https://bugs.freedesktop.org/show_bug.cgi?id=21861#c4
Comment 1 GitLab Migration User 2018-08-10 20:06:06 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libxrandr/issues/1.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.