BandiPat wrote:
On Tuesday 26 August 2003 10:44 am, Basil Chupin wrote:
OK, I've done everything you have said but have struck a brickwall and don't know how to overcome - especially since it all looks so illogical.
During the first installation of the rpms, I got an error message stating that "libwmf-0.2.8-24.i586.rpm did not appear to be a RPM package". All the other rpms installed perfectly. After this I went to have a look at libwmf using Midnight Commander and Yes, mc came back with the message that it could not read the file. So I downloaded another copy of it from the SuSE site and this time I was able to look insided it using mc. Fine, I thought to myself, now I can install it. HA! :-(
When I try to install libwmf-0.2.8-24.i586.rpm I now get an error message which states-
wv requires libwmf-0.2.so.6 wv requires libwmflite-0.2.so.6
and something else also requires the latter file (...lite...).
Now, what has got me absolutely and thoroughly confused is that both of the above files (the so.6) are acutally installed and are sitting in /usr/lib!
What is going on, and what needs to be done to overcome this impasse?
I don't if this connected to the above but before I updated to KDE 3.1.3 - or, rather, almost updated to it - I had a fully functional TV card (ie, Kwintv was working perfectly) and also in the poker game all cards has backs and fronts which were visible- now the cards are total blanks with nothing on them :-).
Anyone have a solution to this problem of mine?
====================
Basil, It turns out the new libwmf rpm SuSE provided for us is bad or at least they didn't settle the dependencies of the other programs that work with the new version. I get the same error, which also includes ImageMagick, so don't force the install, as it will probably break something. Just leave it for the moment, no biggy, and things will come together later.
Not sure if the libwmf plays any part in the poker game or not as mine has been broken for a long time. I suspect it is because the game itself has not kept up with KDE. I find some other anomalies as well and am pretty sure QT3 may be part of the answer. Hopefully kpoker will be brought up to date or qt3 will be corrected, whichever it takes.
Regards, Pat
Thanks for the response. I'm keeping an eye out for an update of libwmf. I've had no problems with kpoker until installing KDE313, but this is the least of my troubles. Another has come up today which is bigger and more worrying. Yesterday after I booted up my computer for the first time, after installing the new KDE rpms, I tried to copy a file across from my other drive to the SuSE installation only to get the message that I had no disk space! I checked - df - and found that I had 0 bytes on my main drive. This was not possible. So I deleted all the KDE RPMs I installed (I think they total 226Mb) and only "got back" some 105Kb of space -- another stupidity. I rebooted the whole system and this time df showed that I had 1.7Gb free which is what I expected to see all along. But then Idid something last night which I now may regret. Last night I checked the SuSE site and found that there were new updates to KDE rpms dated 26/8 so I downloaded and installed them. Everything seemed fine for the short period between installing the new RPMs and going to bed. Today I boot my computer and several minutes later I got the BSD! While I was trying to read what the error messages were, the desktop came back but somewhat corrupted. I rebooted and things appeared to be normal until..... In trying to get Kwintv to work I went to the module.conf file in /etc to see what parameters were set for the bttv option. I used CTRL-ALT-F2, logged on root and checked, and altered, the module.conf file for the tuner setting (which was reading -1 for some unknown reason). (I have to add here that I've edited this file in the past many time without problems). After the edit I pressed CTRL-ALT-F7 to get back to the Desktop -- and ended up with a black screen on which tons of lines of scrolling tryint to dump some information from somewhere :-(. I hit the mouse button and the Desktop came up looking as normal as always. I repeated this process (going to F2 and then back to F7) and this time I caught a message stating something about a "kernel something-or-other"; I then pressed the mouse button again and the Desktop came up again. But this time I decided that I had better reply to your message before something else, more drastic, happened. I think I'll re-install SuSE tomorrow, and I will not waste any more time on KDE 313. Cheers. PS Two other things I forgot to mention. The first is that when I installed the first lot of KDE RPMs the settings/operation of my modem were all screwed up and I couldn't connect to the net (I had to rerun the config file for my modem before it would work). And the second is that I now have a screensaver which cuts in after a few minutes and which I cannot get rid of. The screensaver is NOT set in the desktop configuration, but it just keeps coming up. -- Understanding only begins with the act of perception.