SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had issues testing the upgrade here with slackpkg, where a couple of packages (pango, for example) were skipped because the checksums on the mirror I chose did not match. I ran upgradepkg --install-new on all the -current packages and it fixed it right up. I would run the usual sequence given in the slackpkg man page again and watch to see if it says that any packages are being skipped. If so, upgradepkg --install-new those manually.
If i remember correctly i received a few warnings about checksums when i upgraded. I think i'll start over with 13.1 (ive broken a few things since) then try upgrading that way. Cheers.
EDIT: Scrap that, i just reinstalled aaa_elflibs again, rebooted and now everything works!
That's why i love slackware.
Last edited by coralfang; 11-16-2010 at 04:34 PM.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Well, according to all the entries in this thread, I must be in the minority here. I upgraded yesterday & have had no problems on either my desktop or laptop. I do keep to the shallow end of the pool, never use either slackpkg or KDE's desktop effects.
I don't seem to have any errors in /var/log/Xorg.0.log, but X will not start. I get the same SEGMENTATION FAULT Caught signal 11. server aborting as is mentioned in this thread. this line is just after /lib/lib.so.6.
Am I looking at a reinstall? I read alien Bob's blog, but nothing seems to address this. can anyone offer any ideas of what I can try?
I did all the recommended fixes, disable/enable compositing, aaa_elflibs upgrade, and the mesa downgrade to 7.8.2. My X is still hosed, segfault on start-up.
My laptop has the Radeon IGMP340M chipset and all the -current upgrades (except the glibc stuff)
What else can I try?
You need to upgrade fully, including glibc.
If you are running a multilib Slackware64 then the version of your multilib glibc packages must match that of the slackware64-current packages.
When the glibc updates came out, I did let slapt-get do the upgrade, but it left the machine unusable. So I downgraded it using Robbie W.'s instructions.
Do I need to upgrade manually in a particular order?
... Slackware 13.1 came with FreeType 2.3.12, and there were 2.4.0, 2.4.1 and 2.4.2 releases in the meantime, and you just decided to come up now with 2.4.3 updated, buried in this huge pile of other updates. And now there are suggestions to go back to 2.3.12 for those who don't like new rendering of fonts, implying that nothing in -current actually depends on FreeType 2.4.x. So I really can't understand why it was not possible then for example to release updated FreeType in some small batch of updates previously - this way, I would be probably able to find what caused the issue much quicker, as I'd have to check change logs of dozen of packages, instead of thousands in this case.
Geez, I know . . . The nerve of Pat to not pace the progression of the unstable branch of his distro more to your tastes. I can't believe that guy. Doesn't he know that his stable releases aren't good enough for you and that you have to run -current?
I installed the 16 November upgrades and additions this morning, but it changed nothing.
KDE still crashes shortly after launching.
Xfce still runs fine.
I noticed that you mentioned KDE 4.5.3. The version that I am using, installed from "current" is KDE 4.5.1. Did you update from the KDE site, or has "current" moved up to KDE 4.5.3?
If you want to investigate your KDE crashes further, I have two suggestions that might shed some light on the problem. Create a new, virgin account and then try to start up KDE from that. KDE sometimes has problems with files created by older versions of KDE. Test with a non-proprietary graphics driver that is part of the distro. For example, use the VESA driver. If that stops KDE from crashing then the problem may actually be the graphics driver.
I use XFCE 4 quite a lot and one can even run the KDE programs from XFCE 4. The only thing that I have trouble with in XFCE 4 is accessing network folders. That's probably because I don't know how rather than an actual limitation of THUNAR (sp?).
Distribution: Slackware64-current with "True Multilib." FreeBSD.
[QUOTE=Erik_FL;4162067]I noticed that you mentioned KDE 4.5.3. The version that I am using, installed from "current" is KDE 4.5.1. Did you update from the KDE site, or has "current" moved up to KDE 4.5.3?/QUOTE]
Thanks for the suggestions, but the KDE programs I like and use run just
fine in Xfce so there is little to no need to run KDE itself and all the
bloat that comes with it.
That is the only reason I have KDE installed. Some apps I use will run with other desktops.
Today I tried to sync my Slackware-current. Well...that did not go as it should. My installation was until today a Slackware-current with Gsb-current. A very nice system to work with.
The upgrade done with slapt-get went all okay. Of cource the aaa_elflibs were not installed, so a view of my (kde) apps stopped working. And...the screen fonts were changed :-( . I didn't like this, but sometimes things are as they are.
Upgrading the aaa_elflib like Alien Bob mentioned had as result that the Xserver got broken. Hmmm, I did not upgrade the gtk+2 and glibc packages. Upgrading these would solve the broken Xserver, but will most likely break my gsb setup.
So I downgraded to 13.1 and got every thing working (again). my conclusion: Slackware-current & Gsb-current can not be installed together. I really regret this, because I really like to run current.
NB: I upgraded from kde 3.5 to kde4, but really don't like it so I switched to gsb.