Hello all,

yesterday evening I upgraded my laptop from FC3 (latest kernel) to FC4 via dvd, took ages (3 hours) with a result +/- ok

my winmodem is dead as usual (found some hack and hope it works)

but more disturbing is via KDE 3.4 I can't acces the services menu, it worked ok under FC3

when I choose the menu, it comes up 'grayed' and just dies.....

after the upgrade many services are running (I don't need them)

I tried to find some clues in /var/log/messages etc but.... nothing which is weird for linux since it logs almost each key you strike

someone had similar problem and solved it or has any link with some solutions ?

appreciate your help

eric

I have had the same problem, Try upgrading KDE. I prefer synaptic for rpm, buy rou can also use the RedHat Network to upgrade it. It solved the problem for me.

ok, will try to do so after I get my "smart" winmodem alive (am at work now...)

thanks for the hint

eric

sorry to come back on this way late but I was a little short on time

I upgraded KDE (erased and re installed) but no solution for my services menu

there is no trace in any log except some times in secure :

Nov 21 07:47:27 local@localhost userhelper[4027]: pam_timestamp: updated timestamp file `/var/run/sudo/eric/unknow$
Nov 21 07:47:27 local@localhost userhelper[4031]: running '/usr/sbin/system-config-services' with root privileges $


basically it asks root password and then the menu opens greyed out and pops away again, this is true for user, root in kde, gnome or whatever, no way to get it open.


I did manage partly my services via chkconfig but it isn't the easiest way

thanks for helping me out witht this or at least point my nose in the good direction.

you might want to check the KDE website and their forums (I believe they have one) and see if someone there knows of a solution. That's a tough one. I too have FC4 Full install and since updating KDE have had no problem, I use gnome for the most part, but I don't think that is the core of your problem. Hopefuly someone else can help you with this. Have you tried running KDE under root? just an Idea.

Good luck

don't think it is KDE related, ran root and even logged as root under gnome

same problem, seems the script to work on service is having a problem but I can't trace errors so I have no clue where to start looking except telling what happens, it must be on a deeper level unregarding what front I use, KDE Gnome or any other installed.

Oh well, if someone has some elads where to look, I'm taker

elese it will be chkconfig all the way, hard way is possible too

thanks