Hello LQ!

I just tried to update pidgin (small update, from 2.4.0 to 2.4.1) with the package from linuxpackages.net.

When I tried to run it it didn't work, so, I tried running it from konsole and got this error:

Then, I searched on google and found the GStreamer 0.10.19, and set it up. Now, when I try to run pidgin, I get:

Any suggestions? Thanks in advance.

I never install packages from linuxpackages.net. I always upgrade my applications using official packages from slackware.com or I use slack build scripts. Maybe remove that package and try an official package.

http://slackware.cs.utah.edu/pub/slackware/

So, following advice, I search over the internet for official packages (read: packages.slackware.it).

After solving several dependencies (using the same site), now the error comes to:

I'm starting to think I will need to update de whole system.

I used to be like you myself. As you can see, I use Slackware 12.0 , which on fresh install, it's came with pidgin 2.0.8 or so. If I use slackpkg to upgrade it to 2.4.1, I got the same error as yours.

Just like GIMP, if I use slackpkg to upgrade it, it won't work either. So I download the source and use src2pkg to compile them and both of them work like a charm.

So, I would suggest you to try to compile it yourself. If you want to pack it up for easier to uninstall in the future, use src2pkg.

There was a post here, but I changed my mind. Carry on.

If your getting those undefined symbols, then the pidgin package was compiled against a newer glib than what you have. Either continue playing the updating game until all dependencies are met (installing an updated glib) or build pidgin yourself.

And, yes, stay away from linuxpackages.net... Most packages there are compiled against things that don't even ship with Slackware. eg - gstreamer.... If you don't mind installing tons of unsupported packages, then by all means, you can continue to use linuxpackages.

Don't blame slackpkg. It sounds like you were telling slackpkg to use the repository for a different Slackware version than you actually had installed. Many people do that, and almost without exception, they run into problems sooner or later (usually sooner).

Since you don't (or at least didn't) seem to know the difference, Slackware -current is the development version of Slackware. It's not promised to be stable, and more importantly, the packages in the -current repo are NOT for stable releases of Slackware.

I did not blame slackpkg. I just share my experience with Pidgin here. I use slackpkg myself too, like when I'm trying to compile the Filezilla, it's need a newer version of gnutls, so I use slackpkg to upgrade the gnutls and then use src2pkg for Filezilla.

Hi again!

So i use slackpkg to update to slackware-current and now I can't boot! I normally get pissed off but this time it's just like (forgive me for this) "LOL".

I installed the packages for kernel 2.6.24, and removed my old 2.6.17.13 (from the S11.0 cdrom). After that I couldn't start X, ALSA or muy eth0 interface (also the commands "ifconfig" and "route" were missing). I could still login to the system without a bootdisk.

Then I thought "This can't be so bad, I just have to install the old kernel packages from the cdrom and delete the new ones, right?". BAD IDEA. Before prompting for login I get a message from the system "being unable to run agetty". It repeats several dozen times and then it claims "there is nothing more to be done for this runlevel". And the system instantly crashes.

I can't format (sensitive information not belonging to me is in the hard drive). I was thinking that maybe making a symlink at /sbin/agetty that points to /sbin/getty might work, but, as you can see from the previous paragraph, thinking is not precisley the best of my skills. Is my latest thought a good idea? Thanks.

You could boot the slackware disk and backup the sensitive data on your harddrive, which you should have done anyhow. I would backup my data and get slackware 12.1 and install that if you want newer applications

I JUST told you not to do that. Geez.

http://rlworkman.net/howtos/glibc-recovery

I think you mean http://rlworkman.net/howtos/glibc-recovery (And it's your link, too! )

Indeed; thanks