KDE 4.10.0 upgrade

TroN-0074 · 02-15-2013, 04:00 PM

So I followed the steps to upgrade KDE from 4.8.5 to 4.10.0 from the Alien pastures KTown and everything went well. I was a little scare to mess things up like I always do but it worked fine.

However I think KDE is a little too much for my T42 Thinkpad Pentium IV but I had to do the upgrade for academic reasons mainly.
Thank you Alien Bob for providing this package.

hitest · 02-16-2013, 12:09 PM

Quote:

Originally Posted by TroN-0074

However I think KDE is a little too much for my T42 Thinkpad Pentium IV but I had to do the upgrade for academic reasons mainly.

I'm running Slackware 14.0 and Slackware-current on several older boxes.

Code:

Linux odin 3.2.29-smp #2 SMP Mon Sep 17 13:16:43 CDT 2012 i686 Intel(R) Pentium(R) D CPU 3.20GHz GenuineIntel GNU/Linux

KDE 4.10 will run on my units, but it is not as responsive as I would like. I really like and run XFce 4.10 on my PCs. XFce has the right blend of functionality and responsiveness to meet my needs.

TroN-0074 · 02-18-2013, 05:26 PM

Yes. I mean the laptop runs KDE, however it does a little slow. So what I wanted to say is that instead of using that processing power just to display the graphical interface it would be better to use it doing actual computing calculations and other tasks.

I needed to do the upgrade just to learn how is done.

Thank you.

TroN-0074 · 02-24-2013, 09:17 AM

Weird thing happened, I ran all the updates available last night and after the updates were done it put me back on KDE 4.8.5. And now I am experiencing crashes too, after a few minutes session keyboard input is lost and mouse input is lost too. So I dont know if that was expected behavior, not expected by me though.

I thought to share that little experience here with all.

Thank you

dimm0k · 02-24-2013, 09:49 AM

Quote:

Originally Posted by TroN-0074

Weird thing happened, I ran all the updates available last night and after the updates were done it put me back on KDE 4.8.5. And now I am experiencing crashes too, after a few minutes session keyboard input is lost and mouse input is lost too. So I dont know if that was expected behavior, not expected by me though.

I thought to share that little experience here with all.

Thank you

If you used slackpkg to do the updates and didn't blacklist [0-9]+alien then slackpkg will revert back to KDE 4.8.5. If that's the case, that would explain the odd behavior and probably the crashes too. KDE is pretty finicky going from version to version...

BrZ · 02-24-2013, 03:09 PM

4.10 is being my best KDE4 experience. Some glitches with OpenGL, but Native XRender does teh trick. Latest X improved a lot my system. Thanks crew, -current is fantastic ;]

smoooth103 · 02-24-2013, 07:29 PM

I've always used KDE as my default WM but after this upgrade I really noticed quite a bit of sluggishness -- more than usual. Also noticed quite a few random crashes and some quirky issues. I am *now* using XFCE. I intend to go back to KDE when they polish it up a bit more.

TroN-0074 · 02-24-2013, 07:34 PM

Quote:

Originally Posted by dimm0k

If you used slackpkg to do the updates and didn't blacklist [0-9]+alien then slackpkg will revert back to KDE 4.8.5. If that's the case, that would explain the odd behavior and probably the crashes too. KDE is pretty finicky going from version to version...

I ran the commands again to restore KDE 4.10.0 and is working the way it was before, however I dont know how to blacklist [0-9]+alien so that wont get affected next time there are updates available for slackware.

I will appreciate all advice. Thank you.

dimm0k · 02-24-2013, 11:59 PM

Quote:

Originally Posted by TroN-0074

I ran the commands again to restore KDE 4.10.0 and is working the way it was before, however I dont know how to blacklist [0-9]+alien so that wont get affected next time there are updates available for slackware.

I will appreciate all advice. Thank you.

If you look in /etc/slackpkg/ you should see a file named blacklist. Simply put [0-9]alien at the end of the file and that should be it. You should really look at the list of packages that are going to be modified by slackpkg when you use it to upgrade the system. That way you won't end up in situations like this...

Alien Bob · 02-25-2013, 05:14 AM

See also : http://docs.slackware.com/slackware:...g#blacklisting

Eric

TroN-0074 · 02-26-2013, 04:49 PM

Thank you all for the info. I checked out the blacklist file and added the needed line. Hopefully it will work next upgrade.

Thank you.