rawhide report: 20060726 mesa changes?

[Jim Cornette]

Tom London wrote:
> On 7/26/06, Jim Cornette <fct-cornette at insight.rr.com> wrote:
>> buildsys at redhat.com wrote:
>> > mesa-6.5-19.fc6
>> > ---------------
>> > * Tue Jul 25 2006 Adam Jackson <ajackson at redhat.com> 6.5-19.fc6
>> > - Disable TLS dispatch, it's selinux-hostile.
>> >
>>
>> Can someone confirm if this change allows logging in with SELinux in
>> enforcing and execmem enabled?
>> I opened up the bug below. However, I removed the Fedora Test
>> installation yesterday and cannot verify it is fixed.
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199886
>>
>> Thanks
>> Jim
>>
> Confirmed. But then, it was working for me before this.
>
> What exactly are the symptoms of the problem? Does panel come up?
>
> tom
The panel comes up with all of the icons and menus. I believe the four 
desktop applet does not display.

With SELinux in enforcing and no SELinux parameters to the kernel, 
metacity would not start. What you would get is any application that was 
saved being pegged to the upper left corner as described by another 
user. Only the last application could be used and you could not resize 
it, move it or various other manipulation to the program space. (auto login)
Also, when logging in through gdm and launching gnome, there was  
symptom where the splash screen would stop while loading the first ICON 
and the process which was represented by the icon on the splash screen. 
I assume it was metacity since the text displayed in the splash screen 
listed metacity.

Anyway, I read the change to mesa, which listed SELinux did not like the 
patch and mesa-libGL being the error presented in the shell that 
metacity was launched from. I wondered if this mesa fix was the solution 
to the mesa-libGL problem which halted metacity.

Since I had to give the laptop back to its true owner and removed the 
development installation prior to seeing the rawhide report. I am unable 
to see for myself if I should close the bug as fixed or wait until I 
setup another development installation to check.

Jim