Bug 479532 - texturedXrender enabled crashes X
Summary: texturedXrender enabled crashes X
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drivers
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-10 19:08 UTC by Eddie Lania
Modified: 2018-04-11 09:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-10 22:27:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Eddie Lania 2009-01-10 19:08:21 UTC
Description of problem: Using fglrx driver and texturedXrender enabled causes X unable to start (Segfault).


Version-Release number of selected component (if applicable):

xorg-x11-server-devel-1.5.3-6.fc10.i386
xorg-x11-server-Xorg-1.5.3-6.fc10.i386
xorg-x11-server-utils-7.4-3.fc10.i386
xorg-x11-server-common-1.5.3-6.fc10.i386

fedora-release-10-1.noarch

kmod-fglrx-2.6.27.9-159.fc10.i686-8.561-2.8.12.fc10.2.i686
xorg-x11-drv-fglrx-libs-8.561-6.8.12.fc10.i386
kmod-fglrx-8.561-2.8.12.fc10.2.i686
xorg-x11-drv-fglrx-8.561-6.8.12.fc10.i386


How reproducible: Use fglrx driver and enable texturedXrender.


Steps to Reproduce:
1. Install Fedora 10

2. Install fglrx driver

3. Put 'Option "texturedxrender" "on"' in xorg.conf in the Device section.

4. Put 'Option "RENDER" "Enable"' in xorg.conf in the Extensions section.


  
Actual results: X is unable to start


Expected results: X is able to start


Additional info:

Comment 1 Matěj Cepl 2009-01-10 22:27:43 UTC
Thanks for the report. We are sorry that we cannot help you with your problem, but we are not able to support binary-only drivers. If you would be able to reproduce this issue using only open source software, please, reopen this bug with the additional information, but in meantime I have no choice than to close this bug as CANTFIX (because we really cannot fix it).


Note You need to log in before you can comment on or make changes to this bug.