Gnome window manager is screwed up

[doobie]

I just installed FC5 test3, did a yum update to get everything current and when I logged back in, the 'window manager" initialization part of the Gnome boot sequence stalls. When I finally get into Gnome, none of the windows that I open have borders. It seems to have totally forgotten my theme, but the gnome-theme-manager will not launch because of a libGL.so.1 error (???). However, when I boot into KDE, the windows still show properly. Any suggestions?

[hollovoid]

do you use any graphics drivers, such as ati or nvidia?

[shay]

I have the same problem. I have Geforce FX5200.
I am installing now KDE.
Can not work like that with Gnome.

Looks like the last release of gnome did the problem (or not).
It was ok before I run yum (total update).

Any solution ?

[drunkahol]

Metacity (or something similar) has broken several times during the FC5 test phases. I've ended up using KDE several times.

It wont last more than a day or two at the max before a yum update fixes it.

It is a TEST release after all. If you don't want things to break - don't do any yum updates once you have a stable platform.

Duncan

[shay]

Metacity (or something similar) has broken several times during the FC5 test phases. I've ended up using KDE several times.

It wont last more than a day or two at the max before a yum update fixes it.

It is a TEST release after all. If you don't want things to break - don't do any yum updates once you have a stable platform.

Duncan

Its ok... :)
I will use KDE till they will fix it.

I've notice that you are using ASUS motherboard.
Please take a look on my thread http://forums.fedoraforum.org/forum/showthread.php?t=97318
(SATA support).

[drunkahol]

shay,

Thanks for the link - I'm not planning to put FC5 on my main desktop, however, until the final release comes out.

I'd also stick with the reasonable IDE disks I've already got in it. SATA is certainly tempting, but I'm not a fan of any of these on-board SATA Raid devices that require software drivers. If it requires a driver, then it isn't a complete solution.

The longest I've ended up using KDE due to a Gnome/Metacity problem is 4 days I think. Wasn't too bothered - it allowed me time to get to know KDE a bit better :)

Cheers

Duncan

[dholwerda]

the issue with metacity actually has something to do with SELinux. There is some sort of permission problem with libGLU.so.1.

Turn it off for now by using system-config-securitylevel.

[hollovoid]

dholwerda is right, turning off selinux fixed it for me as well, there may be something you can set in security so that this doesnt happen, but can still have selinux enabled, but havent really looked too much myself.. im sure it will be resolved by final :)