KDE 4.5.0 is available!
… and I can offer you packages for KDE Software Compilation 4.5.0 for Slackware-current. The 4.5.0 packages are accompanied by a README which explains the straight-forward installation/upgrade steps. As always, both 32-bit and 64-bit versions are available.
This marks another milestone for the KDE project with numerous improvements to the KDE 4.4 which we have in Slackware at the moment. Congratulations to everyone who helped in making this release possible, even if its release date slipped a bit instead of delivering on time as usual. The delay allowed for the fix of a few severe application bugs, so in the end we all benefit.
You will need to run Slackware-current dated Saturday July 31, 2010 or newer. My packages for KDE 4.5.0 are not guaranteed to work on Slackware 13.1, so if you want KDE 4.5.0 you are encouraged to upgrade to Slackware-current!
The additional dependencies which you have to take care of on slackware-current (i.e. non-KDE and/or non-Slackware packages) are limited to just one package, thanks to Pat Volkerding who applied several updates to Slackware-current recently – so that the requirements for running KDE 4.5.0 would be met from the start. That single remaining dependency is libdbusmenu-qt (which does not yet exist in Slackware). You’ll find it in the “deps” directory.
If you are adventurous and want to try this on Slackware 13.1 anyway, I think you could get lucky by installing/upgrading the packages which you will find in the “deps” directory of my KDE 4.4.5 package repository for Slackware 13.1. Basically, all those updated “deps” packages are are the real difference between Slackware-13.1 and slackware-current at this moment.
The kdepim and kdepim-runtime packages are not part of KDE 4.5.0 !!
The PIM developers decided that their applications are not yet stable enough to get included, and instead you are encouraged to keep the kdepim and kdepim-runtime packages of Slackware 13.1 (version 4.4.3) or slackware-current (version 4.4.5).
There is one caveat: the consequence is that you will only be able to use the english localization of kdepim, because the language files are contained in the kde-l10n-* packages of the old version. You can not install that in parallel with the 4.5.0 version of your language files. Perhaps I will try and split off the kdepim language files into separate packages, if I have the time (unfortunately at this moment I do not have that luxury).
If you have been running my previous alpha or beta builds of KDE 4.5.0, and if you experience strange application or plasma behaviour in 4.5.0, try with a fresh user profile. Data migration from KDE 4.4.x to 4.5.0 should not be an issue, but there may be some incompatible changes during the early betas, as mentioned by Maciej on Aaron Seigo’s blog.
And in case you think, “what a strange location for the packages, why have they not been placed in the ‘ktown’ repository“… that is a good question! By the time this post appears on my blog, I will not be connected to the Internet. Therefore I have scheduled this post to be published in the future after I finished compiling. And since I could not make the packages publicly available ahead of the official release, I decided to hide them in plain sight… Once I get my Internet back I will move the 4.5.0 packages to the correct location, which is indeed my ktown repository.
Update (22-aug-2010): the 4.5.0 directory has finally been moved into my ktown repository and I have updated the links in this article which point to it.
my install is current 2010-8-3
should i only install kde 4.5 package ?
Pingback: Tweets that mention Alien Pastures » KDE 4.5.0 -- Topsy.com
As usual: Thanks Eric!
waiting to be moved to KTown repo
Wow..more “stuff” to play with. Many thanks for your work Eric !
Yes Eric, it works very well over slackware64 13.1 thanks! 1 day testing it, no bugs.
Thanks again Eric! I’m downloading now.
Confirmed working well on 32bit systems 🙂
Thanks very much!
FYI, there is a _build_polkit.log file in dep ;P
Hello, Any rsync feed available (or will that be available when your net comes back)?? Thanks again for all your hard work. ===Rich
for temporary KDE SC 4.5.0 Repository:
Is it necessary to upgrade to the recent packages akonadi-1.4.0, soprano-2.4.64 and virtuoso-ose-6.1.2?
I have some issues:
dolphin keeps dieng on me for no reason at all.
My panel has no translucency (compositing is on) … stuff like this … BUT thanks a lot for it!
Thanks for the packages! So far it looks and feels great on my 64bit setup.
They still haven’t fixed the bug related to closing my laptop lid though. It locks up X and I have to control alt backspace to get it back. It’s very annoying to say the least!
Another issue I am seeing is that when I close Amarok, the systray icon doesn’t go away.
#amarok and #kde-dev have not been able to produce it, but I was also able to get it to happen with juk.
@????????? ???????? and @Corey: i don’t have any issues with Dolphin nor Amarok.
Did you upgrade from 4.4.5 or from previous BETA or RC release?
@Willy Sudiarto Raharjo
Hey, thanks for the time and effort in putting that stuff up, and thanks for getting back to me. ===R
@Ralph: yes, it’s some of KDE dependencies (soprano and virtuoso)
@Richard Hoyle: no problem 🙂
I just noticed that it is also happening with kmix.
I’m going to have to go back to the older kde package 🙁
Dolphin highly unstable on KDE 4.5
I myself have experienced several crashes and freezes of Dolphin.
These problems had already been reported several months ago but, probably, the developers were too busy with the aesthetic improvements of KDE 4.5 …
@Ralph: wow, that means i’m quite lucky as i never had this problem so far 🙂
Just today I can finish the download and will play with 4.5.0 all the weekend. Thanks Eric, it’s a lot of work and time shared with us.
I have slack32 Current.
Can I go to KDE 4.5.0 upgrade safely ?
Were is the tutorial easy and simple ?
“stability, the overall polish and performance gain is well noticable”
well, my experience with kde 4.5 is totally opposite, had to back to 4.4.5 which is working flawessly but thanks for packages for testing
yes, it’s that easy 🙂
read the README and you will have a safe upgrade to 4.5.0
Pingback: ????KDE 4.5? | VedaClub
@Willy Sudiarto Raharjo:
In relation to what I have written before about this bug:
the problem disappears by updating to akonadi-1.4.0, soprano-2.4.64 and virtuoso-ose-6.1.2 (Slackware Current).
I was using the previous updates for KDE4-4.4.5.
Forget what I just wrote: the problem is still here and will be fixed in KDE4-4.5.1:
Thanks a lot for the kde4.5 packages. I’ve installed them and so far it’s running fine except that I can’t get konqueror to use webkit. I tried the “keditfiletype text/html” method but webkit is still not listed there even though I already installed compiled and installed the webkitpart from svn://anonsvn.kde.org/home/kde/trunk/extragear/base/kwebkitpart. Does someone have an idea why it’s not working? Sorry for my English, I’m from Madagascar
The unstability in dolphin was patched in KDE 4.5.0 and new source tarballs were generated before releasing those officially. I already had built my packages using that dolphin patch myself. Instead of uploading my set of packages, I re-downloaded all the new source tarballs and recompiled every KDE package. So, my packages should not be affected by the bug mentioned in http://lists.kde.org/?l=kde-release-team&m=128091571809498&w=4
I’m still experiencing this problem. As reported by the same team of KDE, the solution will be available only with version 4.5.1.
A user claims to have resolved by updating to DBus 1.3.x as the patch alone is not sufficient.
OK. I upgraded yesterday to DBus 1.3.1 and, within 24 hours of testing, the problem has never occurred!
DBus 1.3.1 is working perfectly and KDE 4.5 is totally stable.
I finally found the solution regarding the webkit problem. It was a path problem. Once the files moved to the right places, it works.
I upgraded Slackware64 13.1 to current. Then I installed the KDE4.5 packages. Mine was a multilib system before the upgrade. Can I use your multilib packages for 13.1 in the current. Or is there some other way.
Yes you can use the multilib packages from Slackware 13.1. If you want to stay on the edge, you can run the massconvert32.sh script to create a whole new set of compat32 packages.
You do not even have to have a local mirror of a Slackware tree; use the following command to download just the packages you need (using the worldwide distributed mirror servers of kernel.org so it will always be relatively fast for you):
massconvert32.sh -u http://mirrors.kernel.org/slackware/slackware-current/slackware
As always you were helpful.
KDE 4.5.1 has been released a couple of days ago! ^_^
Right now, I’m on 4.5 with slack64-current 😉
Pingback: How to: Install Linux KDE 4.5 | HiTech Dot Com
Pingback: Cómo instalar KDE 4.5 - Experto Geek
Pingback: Cómo instalar KDE 4.5 - MATERIA GEEK