My thoughts on Slackware, life and everything

Tag: kde4 (Page 4 of 4)

Release candidate 1 of KDE SC 4.5

The sources of KDE Software Compilation 4.4.90 (which is  in fact Release Candidate 1 of the upcoming KDE 4.5) have been available on KDE’s ftp server for some days now.

There is still no official announcement from KDE team about this RC1 but it will without doubt appear soon on kde.org after the weekend.

In the meantime I have been building packages (32-bit and 64-bit) that you can install on Slackware 13.1 or -current. See my ktown repository for installation/upgrade instructions.

Please note that this release candidate will likely still have bugs – if you find any please report them to bugs.kde.org so that we can expect a great 4.5 release in august.

You can download 4.4.90 from the server using http:

lftp -c “open http://alien.slackbook.org/ktown/ ; mirror 4.4.90”

or using rsync (mind the dot at the end):

rsync -av rsync://alien.slackbook.org/alien-kde/4.4.90 .

Also next week, there will be a release of KDE SC 4.4.5 (the last in the 4.4 series) and if everything goes as planned, this should end up in slackware-current – meaning, I won’t have to build packages for 4.4.5.

Cheers, Eric

KDE SC 4.4.2 for Slackware… including PolicyKit

KDE SC 4.4.2 (second maintenance release for the 4.4 series ) has been made available and the Slackware packages can be found at http://alien.slackbook.org/ktown/4.4.2/

You can download 32-bit as well as 64-bit packages. Many of the dependencies have been updated, some have been added. Read the README in the top-directory for full installation/upgrade instructions, or look for my older http://alien.slackbook.org/blog/its-been-released-kde-sc-4-4-0/ post.

Note that you have to be running Slackware-current (not older than 30-march-2010) or lots of things will break!

As a special gift on april 1st, I have added PolicyKit and ConsoleKit to the dependencies section. The KDE SC 4.4.2 packages have been built with support for them, which means you can now properly set your date/time in KDE, as well as install new fonts and configure your printer… thanks to the work of PiterPUNK and Robby Workman, and NaCl (from the WICD developer team) who wrote and refined the patch for polkit-1 that allowed me to add it without the need for PAM.

This upgrade is recommended if you are using my earlier 4.4.x packages.

Eric

It’s been released: KDE SC 4.4.0

The KDE community has announced the immediate availability of the KDE Software Compilation 4.4.0 (“KDE SC” is the new name of what used to be called just “KDE“). In preparation for this event, the kde.org website was re-vamped yesterday to reflect their “shift in marketing and promotion vocabulary”. Looks shiny and new! Also, I think that the new layout makes it easier for people to find information about the KDE community and the software compilation.

Users of small form-factor laptops will be interested to learn that the new Plasma desktop manager now offers two workspace choices. One is the usual desktop-oriented workspace. The interesting addition is a netbook-oriented workspace, with special consideration for the netbook’s smaller screen and typical mobile usage patterns. I have not yet installed KDE 4.4 on my own Asus EEE netbook but I will most certainly do so, later this week!

In order to fully appreciate the work that went into KDE SC 4.4 and learn what has changed since KDE 4.3, you should definitely take the visual tour. Lots of new functionality and usability improvements are hidden beneath this new desktop workspace and just waiting to be discovered and used to the fullest.

Slackware packages galore!

Like I did with the pre-releases of KDE 4.4, I have prepared new goodies for all you Slackers. Get those 32-bit and 64-bit packages for Slackware Linux and install them on your computers (or build them yourself using the accompanying SlackBuild scripts, patches and sources).

You will find all of those at http://alien.slackbook.org/ktown/4.4.0/ .

Please take good notice of the fact that these packages are built for Slackware-current. You can safely install the KDE 4.4.0 packages if you are running a slackware-current from around 01 february 2010 or newer. Do not try to install these packages on Slackware 13.0.

Slackware 64-bit:

  • Don’t forget to also install the updated or new dependencies! These “deps” packages can be found in the “x86_64/deps” directory.
  • The KDE 4.4.0 packages themselves can be found in “x86_64/kde
  • And of course, the localization packages (non-english language translations of KDE) are available in “x86_64/kdei“.

Slackware 32-bit:

  • Don’t forget to also install the updated or new dependencies! These “deps” packages can be found in the “x86/deps” directory.
  • The KDE 4.4.rc2 packages themselves can be found in “x86/kde
  • If you need a language pack, you can grab one from the 64-bit package tree “x86_64/kdei” since these packages are in fact architecture-independent.

Here are the steps on how you download the packages and install them. You can have an older version of KDE installed, but that is not required. You will end up with KDE 4.4.0 installed on your system.

Instructions are for the 64-bit packages, I think you can figure out how to change them if you want the 32-bit versions:

  1. Download everything in the directory http://alien.slackbook.org/ktown/4.4.0/x86_64/ :
    # lftp -c "open http://alien.slackbook.org/ktown/4.4.0/ ; mirror x86_64"
  2. Change into the directory “x86_64? which has just been created in your current directory:
    # cd x86_64
  3. Remove the no longer required kdelibs-experimental package if you still have that installed. It is part of KDE 4.3.x (i.e. Slackware 13.0 did not have this package). If you do not have kdelibs-experimental on your system, you will get a harmless error message that you can ignore:
    # removepkg kdelibs-experimental
  4. Install/upgrade the KDE 4.4 dependencies:
    # upgradepkg --reinstall --install-new deps/*.t?z
  5. Install/upgrade KDE4.4.0 packages:
  6. # upgradepkg --reinstall --install-new kde/*.t?z
  7. Install/upgrade a language package if you prefer to have the KDE interface in your local language (I used “nl” in the example command, you should substitute your own language code there):
    # upgradepkg --reinstall --install-new kdei/kde-l10n-nl-*.t?z

Of course, you should not run those commands while running KDE…!

If you want to compile the packages from source like I did, that is entirely possible using the provided sources and build scripts. It will take quite a while though…

Have fun, Eric

Note for users of any KDE 4.4 pre-releases:


If you never before installed and used one of the Betas or Release Candidates of KDE 4.4 , then you can safely remove one package,  virtuosoconverter. This package is only needed if you were using “nepomuk desktop search” before this final release of KDE 4.4.0.

# removepkg virtuosoconverter

If you ran any Beta or Release Candidate of KDE 4.4.0 prior to upgrading to 4.4.0, then you will notice that your nepomuk database will automatically be converted from virtuoso v5 to v6, the very first time you login to your KDE 4.4 desktop. This process will take a while (not too long) and will temporarily double the size of your nepomuk database (by default, this database consumes a maximum of 50 MB in your homedirectory below ~/.kde).

If this database is not valuable to you, you can also decide to skip this database conversion by just deleting the database before starting KDE:

$ rm -r ~/.kde/share/apps/nepomuk/repository/*

or by following the instructions in Sebastian Trueg’s tutorial: http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/TipsAndTricks#Remove_all_Strigi-indexed_data

If you manually remove the old nepomuk data, you can also remove the virtuosoconverter package of course.

If you do not have any clue about what I am talking about and what you should do, just don’t do anything… and all will be well.

A final remark about nepomuk and strigi – I think that KDE 4.4 finally has a desktop search which is optimized to a level that it no longer eats all your CPU cycles or claim a large chunk of your harddrive. Now I just wish that the strigi developer properly fixes the indexing of my PDF files!

KDE3, KDE4 and Slackware 13.0

A bit of history… I realized that just a year ago, KDE 4.2.rc1 got added to Slackware’s “/testing” area.

With all the recent posts on this blog about KDE4 and me telling people how nice I think this version of KDE is, I realize that “liking” is a very personal expression of feelings. A feeling shared by many, fortunately, but there are still people who rather have the old KDE3 back, and the perceived stability that comes with it.

Those people should not read the next few paragraphs… instead do a fast-forward to the bottom half of this post 🙂

One of the reasons for the switch to KDE4 in Slackware 13.0 was that I did not want to build KDE3 packages for slackware64 during the time that I was “secretly” building the package set for it. I had been running KDE4 on my Slackware laptop for more than half a year when I kickstarted the 64-bit port in september 2008. Looking at my options for completing slackware64, I decided that I should jump straight to KDE4. It would probably take until somewhere in 2009 before the 64-bit port would be released to the general public. By that time, KDE 4.2 would be available which I thought would be the right time to replace KDE3 in Slackware.

In january 2009, Pat added KDE 4.2.0 to “/testing“, which was essentially a 32-bit “rebuild” of the KDE 4.2.0 packages the Slackware team members were already running on slackware64. Close inspection of the 32-bit KDE SlackBuild scripts would have revealed that something was cooking. The build scripts contained numerous hints to the non-public 64-bit port. By that time I think most of us were running slackware64 on a daily basis and were used to working with KDE4 (well perhaps this is not tru for Robby, our avid XFCE user ;-). The goal for going public with slackware64-current was set for may 2009. This meant that the package sets for 32-bit and 64-bit had to be synchronized before that time. The SlackBuild scripts for slackware64 were written with the philosophy that they should compile 32-bit packages just as easily, so this synchronization effort was not particularly hard, technically speaking… just a tedious administrative job (Pat might disagree here 🙂 The only big change of course, was that KDE4 had to move from “/testing” into the core “/slackware/kde” package directory.

KDE 4.2.1 was the actual version to finally replace KDE3 in Slackware. This was in march 2009, and got big publicity, because it was a revolutionary upgrade and therefore not welcomed by all Slackware users (but what major change is, really). The KDE team on the other hand, was quite pleased about this 😉

Note that I really like KDE4 – it has become so much more powerful a desktop than KDE3 ever was to me. There was just no way that we could keep everybody happy with the switch to KDE4. If Slackware 13.0 had shipped with KDE3, lots of people would have complained about “stale software”, since KDE3 was no longer maintained at that time (3.5.10 was the final release in the series). KDE 4.2.4 which did ship with Slackware 13.0, was good, with rough edges, but the best choice at that time. Since then, Vincent Batts has released a KDE 4.3.1 package set for Slackware 13.0: http://cardinal.lizella.net/~vbatts/kde/kde4-packages/4.3.1/ , slackware-current has moved to KDE 4.3.4 (stable and a joy to use) and my own packages for play-testing the KDE 4.4 prereleases (to be installed on slackware64-current) are mentioned in other blog posts of mine. KDE 4.4 is surrounded by some “political” issues involving the influence of certain big distros, which keep it from being included into Slackware in the near future. Perhaps I should talk about that in more detail, but I will spend another blog post on that.

However, many people have overlooked the fact that Pat actually did create a KDE 3.5.10 package set to accompany the Slackware 13.0 release. Its location is somewhat hidden and there was no publicity on the slackware.com web site. Mainly because KDE 3.5.10 for Slackware was released with status “unsupported“. It was meant as a service to the Slackware users who required more time to make the switch to KDE4.

You can find KDE 3.5.10 for Slackware 13.0 (32-bit as well as 64-bit packages are available) here: http://slackware.osuosl.org/unsupported/kde-3.5.10-for-slack13.0/

Cheers, Eric

Second beta of KDE 4.4

Just before christmas in 2009, the KDE community released the second beta of the upcoming KDE 4.4 desktop environment (or to use the correct name, KDE Software Compilation 4.4).

In Slackware Linux’s development tree we still have 4.3.4 which works really well, but in KDE 4.4 some major strides are being made towards an even better work environment.

I decided to have a look at these new developments, especially since the Nepomuk search should work a lot better with the new and fast Virtuoso backend, and built the whole of KDE 4.4.beta2 for our 64-bit Slackware Linux.

I was not disappointed. Even though this KDE 4.4 prerelease is labeled “beta”, I have found it to be quite stable, fast, slick and very useable. The improvements which I have seen from 4.1 -> 4.2 -> 4.3 -> 4.4 keep amazing me… let alone the giant leap that lay between 4.0 and 4.0… everybody remembers the heated debates between the early adopters of KDE4 and those who hated it. At the time we added KDE4 to Slackware, that was seen as a milestone release. Now, I can not imagine ever going back to using KDE3 as my default desktop. And yes, Nepomuk search is pretty nifty, lightning fast and it does not feel like it is eating away my computer’s resources.

So, I am making my Slackware packages available to the general public – for all of you to enjoy. There is one caveat though:

You will need to run a development snapshot of 64-bit Slackware (meaning, slackware64-current of around 25-december-2009 or newer).

These packages do not work on the 64-bit release of Slackware 13.0. Neither do I have packages for the 32-bit release of slackware-current, simply because I do not have a computer in the house which is running slackware-current and is powerful enough to build KDE4 and the various dependencies in a reasonable time.

KDE 4.4 has requirements that are a bit different than with KDE 4.3.x which we have in slackware-current, or even 4.2.4 which we have in Slackware 13.0. You will have to upgrade several non-KDE Slackware packages as well as add some new ones.

Now, go and have a look at http://alien.slackbook.org/ktown/4.3.85/ . Version 4.3.85 is the same as 4.4.beta2.

  • All of the dependencies that you need are in the “x86_64/deps” directory.
  • All KDE packages can be found in “x86_64/kde”.
  • KDE localizations (language packs) are available in “x86_64/kdei”.

These are the steps you take to upgrade slackware64-current to KDE 4.4.beta2. It will bring you KDE4 even if you did not have it installed before. As part of the steps you will be downloading the new Slackware packages, but not the source or SlackBuilds. It is easy to modify the download command to also get you the sources if you want this.

  1. Download all of the directory http://alien.slackbook.org/ktown/4.3.85/x86_64/ :
    # lftp -c "open http://alien.slackbook.org/ktown/4.3.85/ ; mirror x86_64"
  2. Change into the directory “x86_64” which has been created:
    # cd x86_64
  3. Remove the no longer required kdelibs-experimental package:
    # removepkg kdelibs-experimental
  4. Install/upgrade the new dependencies:
    # upgradepkg --reinstall --install-new deps/*.t?z
  5. Install/upgrade KDE4.4.beta2 packages:
    # upgradepkg --reinstall --install-new kde/*.t?z

Of course, you should not run those commands while running X and certainly not while running KDE… After the upgrade process finishes, you can start a KDE session and you will be greeted by the familiar yet subtly different  user interface of KDE4.

NOTE: Some of the localizations (the KDEI series) had errors while building. Missing from this beta release are the localizations for the following languages:

ca, da, es, et, it, sr.

Here is a screenshot of my desktop with Dolphin showing a Nepomuk-powered search result for the word “slackware” in documents that it indexes, as well as Dolphin’s extremely convenient “terminal mode” (just press F4 to open Dolphin’s terminal if you need the speed of the commandline for some file operation). You’ll also notice that adding widgets to your desktop looks quite different now.

Have fun, Eric

Newer posts »

© 2024 Alien Pastures

Theme by Anders NorenUp ↑