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