Bug 448020

Summary: X crashes if DRI2 is enabled
Product: [Fedora] Fedora Reporter: Ilya Eremin <che_guevara_3>
Component: xorg-x11-drv-i810Assignee: Adam Jackson <ajax>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 10CC: vedran, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-06 08:40:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
X log
none
xorg.conf none

Description Ilya Eremin 2008-05-22 23:18:38 UTC 
I tried enabling DRI 2 in xorg.conf, but seems that it crashes KDE on log in
(with KDE effects enabled).
The error seems to be:
(EE) [drm] Could not set DRM device bus ID.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.

After this it goes back to KDM

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML
Express Integrated Graphics Controller (rev 03)
Comment 1 Ilya Eremin 2008-05-22 23:18:38 UTC 
Created attachment 306429 [details]
X log
Comment 2 Ilya Eremin 2008-05-22 23:19:30 UTC 
Created attachment 306430 [details]
xorg.conf
Comment 3 Ilya Eremin 2008-05-23 08:28:06 UTC 
OK, I was a bit wrong. The crash is due to the other 3 options (still trying to
find out which one exactly). But the bug remains, now I have
direct rendering: No (If you want to find out why, try setting
LIBGL_DEBUG=verbose) and same errors in Xorg.0.log
Comment 4 Bug Zapper 2008-11-26 02:19:35 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Vedran Miletić 2009-09-06 08:40:00 UTC 
I remember having the same issue, but this was fixed long time ago. Reporter, if you are still seeing this, please reopen.