Hey,

The problem I have at the moment, is that when attempting to reach "smb://ginger/Alex Backup" (my backup space on a Windows machine) I recieve the following warning:

After viewing a previous thread and a bit of delving into Google, I have discovered I do have a file kio_smb.la and kio_smb.so in /opt/kde/lib/kde3 and have all of the files needed in a working copy from 'ls -l /usr/bin/smb*'. This is one of quite a few dependancy problems I have encountered after reinstalling Slackware and running slapt-get, but the first one I have no idea how to solve. Any ideas are welcome.

Thanks,
Alex.

Wow. This isn't an answer for you, but an observation: Letting just about any 'automagic' updating program gets you into a situation similar to yours. An updated program needs another, which needs another....

As for starting the ball rolling on the solution, what did you update? What did the changelog say about those programs? Did you follow all the changelog reccomendations?

I can't find any details of this nature for samba, most are merely 'updated samba foo.foo to samba foo.bar'. Yeah, I saw the dependency problems it caused, but I'm not so certain this is due to the updates. I _do_ have kio_smb, it just doesn't seem to be able to use it. According to what I've read this is a part of kdebase, which I have tried reinstalling to no good change.

Your thinking it's a samba problem. It's not. It's a KDE issue. Again, And it IS due to the updates.

I can't find any change notices when searching for 'kde' in the Changelog either. Though, I probably need an older changelog which no longer exists on the mirror, since the upgrade to KDE 3.5.1 isn't in there. Is there a backup kept of the older changelogs somewhere?

Oh, and I upgraded from September's Slackware Official CD. So, KDE 3.4.2 was what I upgraded from (to KDE 3.5.2). One thing I find odd, is that while I have searched other dependancy problems caused by auto updating, I haven't found a single one about this. That was what made me unsure about it being the updates, I can't find a single relevent link.

I meant , did you read the changelogs for each program from it's website BEFORE you tried updating, but from your responses, I'll have to assume you did not, so....

I didn't see the need when I have updated to KDE 3.5.2 from 3.4.2 with no problems whatsoever before. I understand you think me foolish and a newbie, I AM. But, please leave your disdain from a public bulletin board at least. I'll just download all of the new packages, if they work for a new build why not on my current?

You could find downloaded packages in /var/slapt-get/slackware/some-software-series. So open kde folder and try reinstalling them (you should firstly remove the old kde packages with removepkg or using pkgtool, then run installpkg to install new ones).

Thanks for the input Alien_Hominid, that had no effect but I managed to fix it in another way.

Just so you know (everyone bar the immature asses who can't see beyond their own egotistical sense of self-righteousness), I fixed it by using another copy in another folder (xammp) and telling the system to use libraries from there too.

Hello PsychoticDude85! I have the same problem with slackware 11.0 and kde 3.5.4 When I tried to view smb shares from konqueror I've got the same message "Error loading kio_smb.la". I've checked, the files are in place, i've reinstalled kdebase and kdenetwork packages but still no results...Could you, please explain me what exactly have you done to make it work? I've reviewed many other posts on the net about checking for libsmbclient.so.0 (it exsists on my system) and so on, and so on but no any real solution to the problem...I don't won't to recompile the whole KDE on my Athlon 1800+

Well, I cheated really. I downloaded xammp and found that it used the same file for another use. So I added /opt/lampp/lib to my /etc/ld.so.conf file ran ldconfig and then it worked.

This is not doing cwwilson721's remarks any justice.

You seem to have been using an automated update tool on slackware-current (seeing you used KDE 3.5.1 which only was available in the -current development tree for a while, before it got replaced by KDE 3.5.2) and the forum is filled with help requests from people who broke their system using an automated package management tool like slapt-get or swaret on slackware-current.
Generally this is not advisable if you do not also read the ChangeLog.txt very carefully at the same time. You don't seem to have done so. Slackware-current is not meant to be used as a stable environment. It can break from day to day and you should keep to any of the stable releases (10.2, 11.0) unless you are willing to help debug the development process by running slackware-current... but then do not solely depend on slapt-get.

You realize that this does not solve the underlying problem of an ill-configured computer? Something did not upgrade correctly which you fixed by using "computer duct-tape". Who knows, other things might start breaking too sooner or later. You should investigate what went wrong with that KDE upgrade, fixing that will help you in the long run.

Eric

I really do not care, this was from AGES ago as you may have noticed (though I doubt it), and from what I read it seemed all he wanted to do was mock me without even touching on the problem, which I took to be rude.

Anyway, if you want to argue about a five month old comment that's your business, I can't stop you.

And besides, how was I supposed to know how to fix it? It was a problem with a library which just didn't work for no reason I could think of. That was the only fix which worked so I used it. If you think that it was ill-advised then just don't use it. If you have a better method, then post it. I do not see how the upgrades did it because it was in the package, but if you can think of a method of fixing it (given that reinstalling kdebase did NOT work) then please, post away, from what I've seen that's the only method short of recompiling KDE that's been put forward.

You may be glad to know that this isn't even relevant any more because I do follow the changelog, weird how something can change in almost half a year eh? Seriously though, if you want to start talking about post etiquette, then may I put forward a "do not insult someone else's method without putting forward a way it can be improved", just saying "that sucks" is hardly the way to go about it.

Hey, take it easy folks Make peace, not war
Anyway, PsychoticDude85, 10x alot for the answer!! I really didn't have any hopes that you'll answer me Just for the record - I fixed the problem, it was my mistake. In slackware 11.0 (and in the older versions, I assume) in order to use kio_smb io-slave in KDE, you have to have installed
cyrus-sasl-2 and openldap-client packages! Otherwise the kio_smb io-slave will not work! That was it I have missed to put these in my install, so installpkg and everything is fine Again - 10x for the quick answer

Ups, sorry! I've posted the answer twice...somebody delete this