I have recently installed SuSE 10.0 and have almost gotten everything set up. However, YaST has suddenly decided not to let me run most of the tools under most of the categories. Under 'System', it will run the 'PCI Device Driver' and the 'System Services (Runlevel)' tools but no others. I know that I set some runlevel options as I installed but I don't remember running any others in this area.
In other categories, I know that I set several settings but am unable to access those tools now. I was in the process of setting up shares between SuSE Samba and an XP box when I discovered this. I probably inadvertantly changed some setting that is causing the problem.
I do not get an error when I try to run a tool. The clock shows for a few seconds then just disappears and the cursor goes back to the arrow.
Any help would be appreciated.

I am no great authority on this,but you might see if there are any upgrades/patches available for Yast. I am running 9.2, and there have been several things that needed upgraded to run properly. Also, you might chek in the add/remove programs section of Yast and see if the discs came with more than one versin of the program. I don't know of any settings that would make part of Yast unavailable to root! Good luck. By the way have you rebooted since the problem started? Sometimes that at least temporarily fixes things on my system.

Thanks for the response. Actually, this is a brand new install (last Friday). AND, all of the tools were available until just yesterday (Monday). I used several of them during initial setup. Now, for some reason, they are not running. I DID re-boot several times but to no avail.

Consensus is that the update, software package add, or automated updater loaded modules that over wrote part of YaST.

Attempting to re assert the original YaSt would probably have an effect on the system modules that were updated. NOT RECOMMENDED!.

This Blog has funny rules for posting replies and I don't want to spend the day retyping. A useful workaround procedure follows in parts 2 and 3.

First step is to force launch selectors for YAST off line.

I have Suse 10 on an AMD64 with Gnome/GNU.

Place cursor over the "Applications Places Desktop" drop down menu selectors on the top panel. It won't matter which the cursor is over. RIGHT click and select "Edit Menu" option.

There are check boxes that mark whether launcher icons should be visible. For SYSTEM, SYSTEM CONFIGURATION, and PREFERENCES,
deselect YAST. Close saves the work.

Now we need to setup a new launch procedure to enjoy the benefits of a GUI interface to YaST2.

On to Part 3. I repeat, this site has funny posting rules and I don't want to spend the day retyping.

.gaj

We need a new YAST launch procedure.

Place cursor over a blank spot on the desktop. Right Click. Select Create Launcher. A panel with Basic and Advanced tabs comes up.

In the Basic tab, Name: YaST, Command: /sbin/yast2
Click the "No Icon" button and select a .png file. There IS an icon for YaST . You can use it or select another.

In the Advanced Tab, there is a multi box Add/Set Remove line on the lower part of the panel.
First box: POSIX Second Box: YAST Third box: Command Center
Fourth box: <blank or your choice>. Press Add/Set.

There should be a desktop Icon for Yast. Double clicking this Icon should launch the YaST GUI interface.

To make life simpler, RIGHT click the new icon and hold it down while dragging the icon over a panel (top). When the right button is release, a new panel launcher icon should exist.

A single click of the panel icon is sufficient to initiate YAST Gui launch.

Recommend that use is restricted to Root.

This site has funny posting rules. Final remarks are in the next section.

.gaj

A clear indication of YAST launcher being hosed up is to inspect "Properties". Advanced tab (Launcher tab) will indicate a long list of languages.

There is an indication that YAST is soon to be deprecated in favor of some new procedure. When and What is not clear.

Have a good day.

.gaj

PS.

It has been my personal observation that attempting to execute YAST from the menu items (before problems occur but after "updates" have happened) can result in deletion of the root tree. This results in immediate notices of "missing" modules when attempting to launch new processes and if an attempt to log off/log on is made, then additional messages dealing with init.d missing forbids any further process.

Time for emergency recovery procedures. Shame on the developers for releasing with such a major hole in the product.

Make and keep backups, emergency repair disks, and alternative boot disks uptodate. Use of the install CD or DVD can give access to the hosed up system and this is a back door to make a copy of development libraries as a preparation for total system recovery or new install.

.gaj