Hi Folks, Indeed I accept that the Firefox install may not have been the root cause. The only reason I listed it as a suspect was that it was the only thing of significance I could remember taking place between the time yast2 last worked without problem and when it ceased to work. So to be totally honest all I can say is: yast2 is no longer working. What broke it I have no idea! None too helpful methinks! Any suggestions on rectifying the situation gratefully received. Kind regards, Simon Blue Moose IT Support wrote:

Simon Heaton wrote: | Hi Folks, | | Have recently installed SuSE v9.1 Prof. Everything was working fine. | | Installed Firefox (from SuSE rpm) and this seemed to break yast2 as when | I now attempt to start yast2 it dies with the following message: | | warning: the qt frontend is installed but does not work | warning: the ncurses frontend is installed but does not work | You need to install yast2-ncurses to use the YaST2 text mode interface | | Attempting to start yast2 in text mode fails with the message: | | warning: the ncurses frontend is installed but does not work | You need to install yast2-ncurses to use the YaST2 text mode interface | | The yast2-ncurses package is installed as is Qt. | | Any ideas as to what the underlying problem may be? | | Kind regards, | | Simon | Just do what it says and reinstall ncurses and qt from the cd/dvd using rpm instead of Yast.

As the previous poster has stated, this is unlikely to have been caused by installing Firefox.

--S

-- Blue Moose IT Support www.bluemooseit.com

-- Simon JF Heaton Principal Technical Consultant Software AG UK Ltd. Tel: +44(0) 1332 611000 Signature Fpr: 465D 6534 0768 B3EA C564 471B 0BD0 55CB D338 E1DA Encryption Fpr: 94E2 65D9 2473 D1BD 0374 BB22 30E8 7603 731F 6D82 The content of this e-mail is confidential, may contain privileged material and is intended solely for the recipient(s) named above. If you receive this in error, please notify Software AG immediately and delete this e-mail. Software AG (UK) Limited Registered in England & Wales 1310740 Registered Office: Hudson House, Hudson Way, Pride Park, Derby DE24 8HS

Ken Schneider wrote:

On Wed, 2004-07-07 at 07:10, Simon Heaton wrote:

...

Hi Folks,

Indeed I accept that the Firefox install may not have been the root cause. The only reason I listed it as a suspect was that it was the only thing of significance I could remember taking place between the time yast2 last worked without problem and when it ceased to work.

So to be totally honest all I can say is:

yast2 is no longer working. What broke it I have no idea!

None too helpful methinks!

Any suggestions on rectifying the situation gratefully received.

Kind regards,

Simon

You had a suggestion given to you, probably the only one that will work. Use rpm directly.

Mount the DVD/CD that contains the package and use rpm to install it. You can use pin to locate the correct CD if you don't have a DVD drive.

Tried the suggestion. Still the same problem. Kind regards, Simon -- Simon JF Heaton Principal Technical Consultant Software AG UK Ltd. Tel: +44(0) 1332 611000 Signature Fpr: 465D 6534 0768 B3EA C564 471B 0BD0 55CB D338 E1DA Encryption Fpr: 94E2 65D9 2473 D1BD 0374 BB22 30E8 7603 731F 6D82 The content of this e-mail is confidential, may contain privileged material and is intended solely for the recipient(s) named above. If you receive this in error, please notify Software AG immediately and delete this e-mail. Software AG (UK) Limited Registered in England & Wales 1310740 Registered Office: Hudson House, Hudson Way, Pride Park, Derby DE24 8HS

Steve Adams wrote:

On Wed, 2004-07-07 at 04:35, Simon Heaton wrote:

...

Hi Folks,

Have recently installed SuSE v9.1 Prof. Everything was working fine.

Installed Firefox (from SuSE rpm) and this seemed to break yast2 as when I now attempt to start yast2 it dies with the following message:

warning: the qt frontend is installed but does not work warning: the ncurses frontend is installed but does not work You need to install yast2-ncurses to use the YaST2 text mode interface

Attempting to start yast2 in text mode fails with the message:

warning: the ncurses frontend is installed but does not work You need to install yast2-ncurses to use the YaST2 text mode interface

The yast2-ncurses package is installed as is Qt.

Any ideas as to what the underlying problem may be?

Kind regards,

Simon

I had this same thing happen to me when I upgraded from 8.2 to 9.1. To fix it, I booted to CD1, told it to do an installation, went through a couple of screens for language selection, etc., and then selected 'repair' from the choices presented. I had it do an 'automatic' repair. That fixed it. No idea why or what.

hth, Steve

Hi Steve, Thanks a lot for this advice. It worked a treat. But like you, I could not spot what it was that actually fixed the problem. I would like to know how it arose in the first place so that I could avoid a reoccurrence. Kind regards, Simon -- Simon JF Heaton Principal Technical Consultant Software AG UK Ltd. Tel: +44(0) 1332 611000 Signature Fpr: 465D 6534 0768 B3EA C564 471B 0BD0 55CB D338 E1DA Encryption Fpr: 94E2 65D9 2473 D1BD 0374 BB22 30E8 7603 731F 6D82 The content of this e-mail is confidential, may contain privileged material and is intended solely for the recipient(s) named above. If you receive this in error, please notify Software AG immediately and delete this e-mail. Software AG (UK) Limited Registered in England & Wales 1310740 Registered Office: Hudson House, Hudson Way, Pride Park, Derby DE24 8HS

Thursday, July 8, 2004, 11:24:08 AM, you wrote: BMIS> -----BEGIN PGP SIGNED MESSAGE----- BMIS> Hash: SHA1 BMIS> | Hi Steve, BMIS> | BMIS> | Thanks a lot for this advice. It worked a treat. But like you, I could BMIS> | not spot what it was that actually fixed the problem. I would like to BMIS> | know how it arose in the first place so that I could avoid a reoccurrence. BMIS> | BMIS> | Kind regards, BMIS> | BMIS> | Simon BMIS> | BMIS> Just don't do whatever it was you did just prior to the problem occuring BMIS> again! :-) BMIS> (I'm kidding of course) BMIS> - --Sayf BMIS> - -- BMIS> Blue Moose IT Support BMIS> www.bluemooseit.com BMIS> -----BEGIN PGP SIGNATURE----- BMIS> Version: GnuPG v1.2.4 (GNU/Linux) BMIS> iD8DBQFA7RK3h6qZaDhhuVMRAmIuAJ9hpCTk4weqoQSMelO8lCDAhotv8QCgjb0b BMIS> 72fAOhFgyfNaNiPjQJDpdms= BMIS> =gmLS BMIS> -----END PGP SIGNATURE----- I have had similar problem and I still have not solved it. I tried every possible solution, one I have not tried (as I dropped Suse and moved on to MEPIS :-)))) ) was emailed to me and is as follows: "i found your question on the mailing list (i'm not a subscriber). think i can share with you my experience. i've had the same problem, but after i updated the "popt" package, YAST2 is working again. (ftp://ftp.nl.uu.net/pub/linux/suse/i386/update/9.1/rpm/i586/popt-1.7-176.3.i586.rpm) hope that helps." -- Best regards, Siwy mailto:s_marek@poczta.onet.pl

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 | Therefore my question: | Where is the config file for wine when it is installed as root and the winecfg | is run as local user, or do I need to download a sample version of the file | from wineHq and then play around with this to edit the drive configuration. | | Thanks for your help in advance. | | Cheers, | Hanno | Hanno, When starting a new thread, please don't do it by replying to another. See if this document answers your question: http://portal.suse.com/sdb/en/2001/04/mbanse_wine.html HTH, - --Sayf - -- Blue Moose IT Support www.bluemooseit.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA7lSph6qZaDhhuVMRAsNmAJ4ovFuV+3IEaSfcer7RZbrtdksQlACfV7fp VkaHCZzj9TuUscREGvccYfY= =5Zxu -----END PGP SIGNATURE-----

On Sat, Jul 10, 2004 at 10:06:56PM -0700, Carl William Spitzer IV wrote:

Anything more recent than Suse 7.3?

CWSIV

On Fri, 09 Jul 2004 09:17:46 +0100 Blue Moose IT Support writes:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

| Therefore my question: | Where is the config file for wine when it is installed as root and the winecfg | is run as local user, or do I need to download a sample version of the file | from wineHq and then play around with this to edit the drive configuration. | | Thanks for your help in advance. | | Cheers, | Hanno

The config file is automatically generated on first startup, and is in ~/.wine/config. Drives are in newer versions defined by symlinks in the directory ~/.wine/dosdevices/ a: -> /media/floppy c: -> $HOME/.wine/...fakewindowsdir... x: -> /tmp z: -> / These are also autogenerated for a new setup. Ciao, Marcus