Bug 1103386

Summary: swrast doesn't seem to work
Product: [Fedora] Fedora Reporter: Aram Agajanian <agajania>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: ajax, ignatenko
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-18 11:42:57 UTC Type: Bug
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
Backtrace of glxgears after segmentation fault none

Description Aram Agajanian 2014-05-30 23:12:11 UTC
Created attachment 901003 [details]
Backtrace of glxgears after segmentation fault

Description of problem:
When I log into a host with "ssh -X" and try to run glxgears, it exits with a segmentation fault.


Version-Release number of selected component (if applicable):
mesa-dri-drivers-9.2.4-1.20131128.fc19.x86_64


How reproducible:
Happens every time.


Steps to Reproduce:
1. Log into a host with "ssh -X <hostname>"
2. Run the command "glxgears"


Actual results:
The program exits with segmentation fault.


Expected results:
A window should appear with turning gears.


Additional info:

The backtrace at the time of the segmentation fault contains a call to radeon_drm_winsys_create().  This seems incorrect.

When I run glxgears with LD_PRELOAD=/usr/lib64/dri/swrast_dri.so, then it works.

glxgears runs OK with software rendering (e.g. ssh -X) when the host OS is Fedora 20.

Comment 1 Aram Agajanian 2014-05-30 23:14:21 UTC
An alternative workaround to LD_PRELOAD would be helpful because setting that seems to break non-glx executables.  For example, if I try to run the "ls" command, the following error occurs:

ls: symbol lookup error: /usr/lib64/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch

Comment 2 Aram Agajanian 2014-06-04 19:07:05 UTC
It was suggested on IRC that the patch that the following URL fixes this problem:

http://cgit.freedesktop.org/mesa/mesa/commit/?id=e3cc0d90e14e62a0a787b6c07a6df0f5c84039be

Using a reubuilt mesa 9.2.4-1.20131128.fc19 with this patch, glxgears runs without having to set LD_PRELOAD.

I haven't yet noticed any problems since installing the rebuilt mesa with this patch.

Comment 3 Fedora End Of Life 2015-01-09 21:23:43 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-18 11:42:57 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.