Bug 706698

Summary: [abrt] glx-utils-7.9-5.fc14: XF86DRIQueryExtension: Process /usr/bin/glxinfo was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: masoudjavadieh <javadieh.msd>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ajax, joe_underscore, ryans
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3085e5cf27a43463cefb3943e37db9f5f4f6a449
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-05 20:19:32 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
File: backtrace none

Description masoudjavadieh 2011-05-22 11:40:03 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 8513 bytes
cmdline: glxinfo
component: mesa
Attached file: coredump, 1495040 bytes
crash_function: XF86DRIQueryExtension
executable: /usr/bin/glxinfo
kernel: 2.6.35.13-91.fc14.i686
package: glx-utils-7.9-5.fc14
rating: 4
reason: Process /usr/bin/glxinfo was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305884718
uid: 500

How to reproduce
-----
1.trying to define xxorg.conf for multiseat
2.
3.
Comment 1 masoudjavadieh 2011-05-22 11:40:08 UTC 
Created attachment 500258 [details]
File: backtrace
Comment 2 masoudjavadieh 2011-05-24 12:09:09 UTC 
Package: glx-utils-7.9-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.due configuring for multiseat
2.
3.
Comment 3 Adam Jackson 2011-05-24 17:30:11 UTC 
Please attach the output of 'rpm -qV mesa-libGL'
Comment 4 Joe Robinson 2011-05-27 18:55:04 UTC 
Package: glx-utils-7.9-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Do it again ...

[whacker@fireball ~]$ glxinfo
name of display: :0.0
Segmentation fault (core dumped)
[whacker@fireball ~]$ glxinfo
name of display: :0.0
Segmentation fault (core dumped)
[whacker@fireball ~]$ 




2.
3.


Comment
-----
[whacker@fireball ~]$ glxinfo
name of display: :0.0
Segmentation fault (core dumped)
[whacker@fireball ~]$
Comment 5 masoudjavadieh 2011-05-28 07:44:21 UTC 
Package: glx-utils-7.9-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.trying to define xxorg.conf for multiseat
2.
3.


Comment
-----
it is the  output of 'rpm -qV mesa-libGL':
[masoud@arya1 ~]$ rpm -qV mesa-libGL
....L....    /usr/lib/libGL.so.1
....L....    /usr/lib/libGL.so.1.2
[masoud@arya1 ~]$
Comment 6 Joe Robinson 2011-05-28 21:49:57 UTC 
Package: glx-utils-7.9-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I had ssh in from the LAN and 'glxinfo'
2. "name of display: localhost:10.0"
3. "Segmentation fault (core dumped)"


Comment
-----
- as above
Comment 7 masoudjavadieh 2011-05-30 11:31:49 UTC 
Package: glx-utils-7.9-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.due configuring for multiseat
2.
3.


Comment
-----
using grafic card with the NVIDIA driver cause this. I read in http://wpkg.org/Configuring_multiseat_X_workstation, that neavou driver cause GLX stop runinng

I read as well GDM2.2 or later does not suport multiseat. 
Maybe the cause of crash rest in GDM2.32.1 which I use
Comment 8 ryans 2011-06-11 06:22:54 UTC 
Package: glx-utils-7.9-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.  Using proprietary ATI Catalyst driver
2.
3.
Comment 9 masoudjavadieh 2011-06-16 10:12:39 UTC 
I removed ATI Cataylyst but glx crashes yet.

(In reply to comment #8)
> Package: glx-utils-7.9-5.fc14
> Architecture: i686
> OS Release: Fedora release 14 (Laughlin)
> 
> 
> How to reproduce
> -----
> 1.  Using proprietary ATI Catalyst driver
> 2.
> 3.
Comment 10 Adam Jackson 2011-07-05 20:19:32 UTC 
These all appear to be bugs in proprietary drivers, closing.