Summary: | crash when running xrandr --query and DRI compiled in | ||
---|---|---|---|
Product: | xorg | Reporter: | Lee Leahu <6khRTwRnE3AB> |
Component: | Server/Ext/DRI | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | ewalsh |
Version: | git | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Lee Leahu
2008-10-08 11:34:37 UTC
This also affects 32bit platforms: - AMD Athlon XP 3000+ - ATI Radeon 9600 The build is based on the git version. Last commit in the git version is 'd744dc013cf5ca3141c0fdf55e36d713fe9f53ba' This seems only to be triggered when the driver is build with dri support enabled. I think this was introduced by xserver commit 4017d3190234e189a0bbd33193a148d4d3c7556b ('devPrivates rework: since API is already broken, switch everything over to new system.'): DRICloseScreen() sets DRIScreenPrivKey = NULL, and there's no code to set it to non-NULL for the next server generation. Eamon, how should this be fixed? Just drop the DRIScreenPrivKey = NULL assignments? Should be fixed in 5b336585a4cdf11d20831a9536ad581e959ea7f1. I tested it and grepped the code for other instances of setting the NULL, but found none. There is also no sane reason to change this pointer imo. Confirming fixed in 5b336585a4cdf11d20831a9536ad581e959ea7f1. |
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.