SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After installing Suse 9.1 successfully I proceeded to the online update in YaST. It stopped downloading at an Open Office file, so I aborted the update. It completed the system re-configuration, but when I tried to start YaST again it wouldn't start. I tried it from the command line and got the following error:-
warning: the ncurses frontend is installed but does not work
You need to install yast2-ncurses to use the YaST2 text mode interface
How do I install yast2-ncurses if YaST isn't working or how do I do a complete reinstall of YaST?
If you can find the package, you could use the "rpm" command.
rpm -Uhv <package-name>
to install the package.
Also, you might try "yast -i <package-name>" which might not need the curses library.
One other thing to try is to run the "SuSEconfig" script. Since you aborted the update, it probably wasn't run. Also try running the "ldconfig" command. It might be the case were needed libraries are installed but not entered in ld.so.cache.
A while back I had the same problem. I think it's the kdebase or kdelibs package that is the culprit. The yast interface is broken so you will need to download the files for kde then run as su:
rpm -Uvh kde*.rpm
Try the kdelibs package first, if that doesn't work then you'll need to download in order the other files and install manually. I remember this was quite a pain to get fixed due to several dependencies.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.