Hi,

As of 3 weeks ago when I start YaST after providing ROOT password, I get the GUI but clicking any program icon won't start it! Also right-clicking and selecting Start does nothing.

I REALLY have to figure this out as I now have no way to run YaST (I did find it runs as root from the command line but it's a different GUI)

I think a recent patch may have done this... Thoughts?

Thanks.

Running: SLED 10 SP1

Try to create a new user and see if YaST works for that user. If it does, consider it your lucky day. Login again with the user you are having trouble with and delete anything starting with a "."(hidden files) at your /home/<user with problem> which you think is related to YaST (don't have SuSE at the moment, so I can't tell you which files to delete, but should be simple).

Best of luck!

I'm not sure about SLED (but I expect it to be the same as OpenSuSE in this regard), but in addition to the above answer and on a temporary basis, you should note that you ought to be able to perform any task that you could from the GUI version of Yast2 from the command line version. OK, its not as pretty, but all the submenu items are arranged in the same way, so you wouldn't have thought it much of a stretch.

Well SuSE's patches really shouldn't have done it. And, if they had, you would have expected thousands of people to be crying/shouting/taking up arms about it, unless there is something really odd that makes it only afect certain installations. So, my first guess would be that the cause lies elsewhere (fwiw).

Try to run YaST2 on a terminal window, not by the menu entry. To do that just open a terminal as root and type "YaST2". After the GUI start up, try to run any module. Look at the terminal window. You will see the command to start the module and any errors following the command. For instance, I clicked on the Services/DNS server icon and I got:
You can call the modules directly, without the YaST2 "big panel". Just use "/sbin/yast2 module-name" as above. To get a list of names for all modules, use "/sbin/yast2 -l".

Calling the modules in a terminal window will print any error in terminal, and the messages can help you to diagnose the problem.

cheers,

Woa !

Why is it I get better support from my SuSE team here than some of the support we PAY for at our company ? ;-)

Anyway, thanks for the responses. Ok this workstation is getting seriously messed up (and I have a boat-load of work to get done in the next 3 weeks!)

I tried creating another user and logging in as him and the desktop wouldn't even start, just a cursor and black screen, twice. Logging in as ROOT I still can't run progies in YaST, however running as me, I can start YaST2 as root from a command prompt and I can start all YaST progies fine now ;-) Cool.

So, I'm going to get ALL recent patched and updates and hope for the best but now I'm wondering, with the SLED 10 cd's is there any sort of a "Repair" option I can use without doing a total format and install?

Also, I'm jealous of my Mac friends and their "Time Machine" backup system. What should I be backing up with the YaST System Backup tool that would have helped me fix this?

Thanks!

Additionally, I found this .xsession-errors file in my home dorectory. DOesn't look good:

/etc/opt/gnome/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/opt/gnome/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "nuro"
/etc/X11/xim: Checking wether an input method should be started.
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
No profile for user 'nuro' found
SESSION_MANAGER=local/ALIEN:/tmp/.ICE-unix/7058

I do get occasional X Session weirdness and have to restart to fix it. Thoughts?