Bug 821137 - Xorg segfault in libglx (Intel HD3000 graphics)
Xorg segfault in libglx (Intel HD3000 graphics)
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-12 07:50 EDT by James
Modified: 2013-05-22 15:53 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-05-22 15:53:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Xorg.0.log of crashed session (32.12 KB, text/plain)
2012-05-12 07:50 EDT, James
no flags Details
dmesg from failed session (73.00 KB, text/plain)
2012-05-12 07:50 EDT, James
no flags Details

  None (edit)
Description James 2012-05-12 07:50:13 EDT
Created attachment 583985 [details]
Xorg.0.log of crashed session

Description of problem:
Clicked on sound icon, went to open Sound Settings. X segfaulted and spontaneously restarted. Xorg.0.log and dmesg attached. No X config files of relevance used.

Not seen this before on this machine (after stable operation so far), but I'd recently updated to mesa 8.0.2-7 from updates-testing. Backtrace seems to indicate libglx as the suspect (is drv-intel still the right place for these reports?).

Version-Release number of selected component (if applicable):
mesa-libGLU-8.0.2-7.fc17.x86_64
kernel-3.3.5-2.fc17.x86_64
mesa-libGL-8.0.2-7.fc17.x86_64
xorg-x11-drv-intel-2.19.0-1.fc17.x86_64
mesa-libglapi-8.0.2-7.fc17.x86_64
mesa-dri-drivers-8.0.2-7.fc17.x86_64

How reproducible:
Unknown.
Comment 1 James 2012-05-12 07:50:46 EDT
Created attachment 583986 [details]
dmesg from failed session
Comment 2 James 2013-05-22 15:53:19 EDT
Not seen in a while. Closing.

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