Bug 88113 - i965_dri.so segfaults and prevents graphic applications from starting
Summary: i965_dri.so segfaults and prevents graphic applications from starting
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 10.3
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-06 14:24 UTC by vonash
Modified: 2017-02-10 22:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description vonash 2015-01-06 14:24:46 UTC 
Blender and Draftsight crash at start with segfault in i965_dri.so. With Draftsight the window opens and crashes at the time of opening the drawing canvas. With Blender the segfault is before opening the window.

System environment:
-- chipset:
-- system architecture: x86_64
-- xf86-video-intel: ??
-- xserver:1.16.2.901 (1.16.3 RC 1)
-- mesa: libgl1-mesa-dri 10.3.2-1: amd64
-- libdrm:2.4.58
-- kernel:3.14-1-amd64
-- Linux distribution: Debian jessie
-- Machine or mobo model: Fujitsu Siemens Lifebook S6410
-- Display connector: none

Reverting to debian stable package 8.0.5-4+deb7u2: amd64 resolves the issue with Blender and Draftsight. Google Map is not showing in Iceweasel 31.3.0 and Chrome Version 39.0.2171.71 Built on 8.0, running on Debian 8.0 (64-bit). But not sure if this is a related issue.

Bug is reproducible 100% of the time.

Possible duplicate is
https://bugs.freedesktop.org/show_bug.cgi?id=79752
Comment 1 Matt Turner 2016-10-31 23:18:59 UTC 
Please try a new version of Mesa and reopen if it still occurs.
Comment 2 Annie 2017-02-10 22:38:58 UTC 
Dear Reporter,

This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested.

Thank you.

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.