Today saw the announcement of a new chapter in the KDE 4.8 series. I was already very pleased with the point release 4.8.0 – it is amazing how the developers managed to keep their desktop environment stable when transitioning from 4.7 to 4.8. And the first maintenance release 4.8.1 brings us bug fixes and more.
Thanks to the fact that the KDE team makes the sources available to packagers ahead of the public announcement, I am again able to provide you with Slackware KDE 4.8.1 packages on time, and they are up for the taking!
It appears that I finally raised Patrick’s interest in the current generation of KDE. He has built his own set of packages and I received excited reports from him. That is a good sign! Perhaps there will be a nice update to slackware-current in a not-too-distant future.
Please note that my own KDE packages have been compiled on Slackware-current. There has been an incompatible update to slackware-current recently (the glibc package) which will cause run-time errors if you attempt to start these KDE programs in Slackware 13.37. If you consider using KDE 4.8.1 on one of Slackware’s earlier (stable) releases, then you have no other option than to compile packages yourself. I have written down the guidelines in another blog post..
Read the accompanying README file for installation and upgrade instructions!
You will find a lot of additional information about what the new KDE offers in comparison to the old version in Slackware, in my announcement post for KDE 4.8.0 Worth checking out if you had not read it before.
Highlight of this new set of Slackware packages:
- I have added Calligra 2.4_rc1. Calligra is the continuation or “fork” if you wish of the old KOffice. Near the end of 2010 there was a fall-out between the developers of the various KOffice components, and the majority (everyone except the KWord developer) walked off to start the Calligra fork. The Calligra office suite is fianlly entering Release Candidate stage, and it is stable enough to use it on a daily basis. Don’t forget to “removepkg koffice”! Calligra’s technology is already being used on tablets: the MeeGo Office suite has Calligra at its core. There is already support for Plasma Active as well, you will find the “Active” applications in your KDE menu.
The KDE 4.8.1 packages for Slackware-current are available for download from my “ktown” repository and several mirrors (taper is in sync when I post this, the other mirrors will catch up soon):
- http://alien.slackbook.org/ktown/4.8.1/ (the master repository), rsync URI: rsync://alien.slackbook.org/alien/ktown/4.8.1/
- http://taper.alienbase.nl/mirrors/alien-kde/4.8.1/ (my fast mirror), rsync URI: rsync://taper.alienbase.nl/mirrors/alien-kde/4.8.1/
- http://repo.ukdw.ac.id/alien-kde/4.8.1/ (willysr’s Indonesian mirror), rsync URI: rsync://repo.ukdw.ac.id/alien-kde/4.8.1/
- http://scw.net.br/alien-ktown/4.8.1/ (a mirror maintained by Herbert Alexander Faleiros), rsync URI: rsync://rsync.scw.net.br/alien-ktown/4.8.1/
Have fun! Eric
Thanks Eric, saw it early this morning and upgraded.
So far no problems and the bugs that trubbled me in 4.8.0 are all gone.
Thanks again! I just upgraded to current yesterday so these packages came at good time for me.
Thanks Eric, great work!
Thanks Eric! Just finished downloading and about to do the upgrade! Much appreciated!!
@Eric: after installing Calligra, I can’t find Kexi anymore.
Thanks Eric, new KDE works great.
Bah, kexi now depends on icu4c. I am not sure if Patrick will be happy with yet another dependency if the package is 7 MB in size…
But, you can install my icu4c package (http://slackware.com/~alien/slackbuilds/icu4c/) and then recompile calligra from source:
# ./KDE.SlackBuild extragear:calligra
I see your oxygen-icons package is named with “i486” or “x86_64” arch, even though it doesn’t contain any binaries. Shouldn’t this be “noarch” instead? And why aren’t there any scalable SWFs inside?
Anyways, thanks for your great work!
Icu4c allows trimming down its data sets to needs. Couldn’t you just build a small, thoroughly castrated version to make kexi happy?
while granularity is fine, i’d suggest to somehow sort or label the packages for those who are not installing everything. With KDE4.8.0 i spent some time to relocate to separate directories edu, utils etc packages, just to have the core without bells and whistles.
Thanks for the tip Eric. I have icu4c installed anyway (dependency for your Calibre package). So i will just recompile Calligra.
Pingback: Links 9/3/2012: KDE 4.8.1, New Wine | Techrights
Thank you, upgraded today, as always no problem.
I ran across a small problem. With the packaged version of Calligra, krita isn’t working right for me. It loads, then crashes complaining that the lcms plugin isn’t installed.
I have lcms2 installed (from SBo) alongside slackware’s lcms 1.x. When I build Calligra from the git sources and install it krita finds the lcms plugin and runs fine.
Are others able to run krita from this Calligra package, or is this just some wierdness on my machine?
Pingback: Alien Pastures » KDE 4.8.1 – the best DE you can get | Linux Blog
Thank you, Eric! If only powerdevil developer had not lost he’s mind, I would hava called it perfect 🙂
Hello Eric. I’ve got error message when open Krita: “The Calligra LittleCMS color management plugin is not installed. Krita will quit now.”
And this is my lcms package in my system:
How can I fix this?
fakhry i got the same error and looks like it needs koffice-plugins.
Same Krita crash here: “The Calligra LittleCMS color management plugin is not installed. Krita will quit now.”
32-bit system with lcms-1.19-i486-1
I’m really enjoying 4.8.1: for the first time phonon is playing well with pulseaudio for me.
It seems that calligra compiles fine but then the krita program crashes if lcms2 was not present during compilation. I talked to Patrick about this, and he answered that he planned to look into lcms2 anyway. I will see if I can add it to my ktown repository and rebuild calligra.
I added a “lcms2” package to the “deps” section and rebuilt calligra. Krito now works here.
The packages have been uploaded to my repository (and the “taper” mirror has them too). Mirrors will follow when they perform their daily re-sync.
Thanks as usual Eric!
thanks Eric. I’ll try then 🙂
Pingback: My weekly Dad’s reads, March 5th to 11th 2012 | 2FatDads
I have updated the sources with rsync, compiled and installed lcms2 from deps and tried to rebuild calligra but I get the following error:
/tmp/kde-build/extragear/calligra-2.3.91/kexi/kexidb/drivers/sqlite/dump/shell.c:2864:18: error: ‘SQLITE_CONFIG_URI’ undeclared (first use in this function)
Apparently SQLITE_CONFIG_URI is not defined in /usr/include/sqlite3.h
Before updating I was able to successfully build calligra but I think that it didn’t include the sqlite3 backend.
I forgot: I am building on 13.37 64 bit
Solved: on 13.37 an upgrade from sqlite-3.7.5 to sqlite-3.7.10 is needed (only for calligra.)
Thanks for your work: I’ve used 4.8.1 only for a couple of days but it looks very promising.
is anyone else having a problem after upgrade tu 4.8.1, the system tray only shows KDE’s icons, things like xchat or skype just don’t show up.
ps. i had 4.8.0 working great, I did a “slackpkg clean-system” then “slackpkg upgrade-all” and then installed multilib and kde4.8.1
Many thanks for sharing these packages. I am building them a 13.37 install, and am getting the following when the slackbuild for libkorrent runs:
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run “cmake –help-policy CMP0000”.
This warning is for project developers. Use -Wno-dev to suppress it.
— Configuring incomplete, errors occurred!
make: *** No targets specified and no makefile found. Stop.
make: *** No targets specified and no makefile found. Stop.
Is this expected on a 13.37 system? I’m not quite sure how to resolve it.
All the best,
OK, this might explain things:
bash-4.1# cmake –help-policy CMP0000
cmake version 2.8.4
A minimum required CMake version must be specified.
CMake requires that projects specify the version of CMake to which
they have been written. This policy has been put in place so users
trying to build the project may be told when they need to update their
CMake. Specifying a version also helps the project build with CMake
versions newer than that specified. Use the cmake_minimum_required
command at the top of your main CMakeLists.txt file:
where “.” is the version of CMake you want to support
(such as “2.6”). The command will ensure that at least the given
version of CMake is running and help newer versions be compatible with
the project. See documentation of cmake_minimum_required for details.
Note that the command invocation must appear in the CMakeLists.txt
file itself; a call in an included file is not sufficient. However,
the cmake_policy command may be called to set policy CMP0000 to OLD or
NEW behavior explicitly. The OLD behavior is to silently ignore the
missing invocation. The NEW behavior is to issue an error instead of
a warning. An included file may set CMP0000 explicitly to affect how
this policy is enforced for the main CMakeLists.txt file.
This policy was introduced in CMake version 2.6.0.
What would you recommend?
I have a constant problem in one instance – kde 4.8.1 constantly forgets folder view settings and after start-up i have empty desktop. Only after switching back and forth to desktop view teh folder view is restored, but – unfortunately, with totally messed up icons.
I have a problem with install and compile DigiKam 2.5.0.
I recompile itself exiv2 and libkexiv2 and DigiKam sucessfully compiled!
But i found new problem
If you use 4.8.1 be careful with update to current from “Mon Mar 26 01:41:11 UTC 2012”. After update, I have problems with KDE startup. It segfaults in ksmserver (and kwin). I try to strace problem, but with strace there is no problem!
So instead of problem detection, I have temporary workaround. If someone have same problem, replace 346 line of /usr/bin/startkde “kwrapper4 ksmserver $KDEWM” by “kwrapper4 strace -f -e trace=fork ksmserver $KDEWM”
If someone ask, “-e trace=fork” is for silence console output. And, as I say this is only TEMPORARY solution as it generate noticeable CPU usage.
I’ve identified my problem. It exist in nvidia proprietary openGL library. Update to latest version available, hopefully fix it.
I enjoy the performance boost of 4.8.0 on my asus 1005ha (small but noticeable).
i’ll have to get find the time to upgrade to 4.8.1… has anybody test it on a netbook?
ok.. as it is friday i took the time to download the packages and update kde on the netbook.
everything works fine as it did before… couple of dependencies where upgraded so no big deal as I was running 4.8.0
left calligra out as i’m running libreoffice… will test later.
I think, ill revert back to 4.8.0 – otherwise the extremely idiotic behaviour of 4.8.1 will lead me to lowing Windows7:
that piece of s.. oft called activities ir messing up everything possible – I use only folder view regime with desktop as only folder displayed. after EACH restart I find my desktop empty, digital clock in non functioning state, only wallpaper and last open app in place. After fiddling around i found that it is somehow possible to create activity “Folder view” and then get my favorite view.
BUT. if ir delete any other trash activities leaving the only i need, after restart I have the same – welcome to the same shitty state.
So – may be there is the knowledge on stripping down “cool” components of kde 4.8.1?
If you think you found a bug introduced with KDE 4.8.1 then the best thing to do is open a bug in KDE’s bugtracker (https://bugs.kde.org/) so that it can get fixed. Whining about going back to Windows7 is not going to give you more credibility however.
I do not know whether it is a bug or not – i just want to get rid of all that marketing nonsense, that’s all, call it Minimalistic KDE. If someone need those “ujactivities”, he is welcome to debug them. I like(d) KDE, even KDE4, but if the only way to use it is to “enjoy” everything invented by KDE team, i’ll finally give up.
I almost agree with you on whining, but during two last weeks I met SO much problems with virtually stable OS software that I am starting to shake in my “faith”.
If you can advice, how to reduce “features” in kde 4.8.1, you comment on it will be very welcome.
If yoiu could work with KDE 4.8.0 but have issues with 4.8.1 then I would call that bugs. It would help if you would describe something that can be tried (and reproduced) by other people too see if it can be solved easily.
I myself have no issues at all with KDE 4.8.1 but perhaps I use different aspects of it. I do not use “activities” for instance.
Comment from Hannibal
Posted: March 27, 2012 at 08:34
Pingback: KDE 4.8 en Slackware « eduardo's blog
Pingback: Amarok doesn't play Mp3s with GStreamer backend - Developer