[elrepo] ATI/AMD and glamor, was Re: NVIDIA and RHEL 6.5 issue (libglamoregl)

[Phil Perry]

On 03/12/13 01:32, Michael Lampe wrote:
> Michael Lampe wrote:
>> Phil Perry wrote:
>>
>>> [root at rhel6b64 ~]# /usr/sbin/lsof | grep X | grep libGL
>>> X         1970      root  mem       REG                9,1  1165272
>>> 797319 /usr/lib64/nvidia/libGL.so.331.20
>>>
>>>
>>> I see this on RHEL6.5 with glamoregl loaded. If I disable glamor then
>>> libGL is no longer loaded into the X process.
>>
>> That's then the unsupported use case. Maybe it's not a problem, because
>> actually Nvidia's driver doesn't use glamor, so libGL is just loaded
>> into the X server doing nothing.
>
> shared libs tend to have constructor and destructor functions, so
> probably more than nothing happens:
>
> http://tldp.org/HOWTO/Program-Library-HOWTO/miscellaneous.html#INIT-AND-CLEANUP
>
>
> Anyway, thanks for pointing this out.
>
> If you have an Nvidia card, at best glamor doesn't hurt. If you have an
> Nvidia card and something else that uses glamor, it won't work. And if
> you don't have an Nvidia card it doesn't matter. To me this clearly
> translates into "Conflicts: ..."
>
> I have removed glamor already yesterday. :)
>

Just to update this thread and add a related data point. We received a 
couple bug reports that the proprietary ATI/AMD drivers were crashing 
after updating to 6.5 and preliminary investigations suggest glamor was 
the culprit. It would appear that for the ATI/AMD drivers, having glamor 
loaded is fatal and causes X to seg fault.

In that particular case, because it's fatal, I'm inclined to add a 
Conflicts and live with the pain.