Category: KDE

In the next hours KDE:Current will publish KDE 4.13 SC. As that this release comes with a big change (Nepomuk -> Baloo), we would like some simple steps in order to perform the right upgrade.

Before the upgrade

In order to migrate data automatically from the Nepomuk store to the new format (used by Baloo), you will need Nepomuk up and running, and just for the time needed for the migration. Ensure that Nepomuk is running before the update (in System Settings > Desktop Search). This is only necessary in case Nepomuk is in use on the system.

The upgrade itself

  • If you are already using KDE:Current then the upgrade should be a simple “zypper up” or upgrade packages through YaST Software Management.
  • If you are not yet using KDE:Current, then please follow the instructions on on how to add the necessary repositories. After adding them, a zypper dup is required to ensure that all the KDE packages are coming from KDE:Current.

Please do not remove nepomuk, as that otherwise the migration to baloo will fail !! Also after the upgrade please make sure that the following package is installed “baloo-file”. After this check, log off and back on. The migrator will then run and move all the data that can be migrated to the new system. It will also turn off Nepomuk at the end of the migration.

At this moment it would be safe to remove the nepomuk related packages like nepomuk-core, libnepomukwidgets, soprano*, strigi, virtuoso and shared-desktop-ontologies. There are only a few packages left that are still

requiring the nepomuk-framework (like bangarang, kweshtunotes, etc).

Using Baloo

Unlike the ‘include folders to be indexed’, Baloo prefers to index everything and exclude unwanted folders explicitly. With the standard setup, Baloo will index all files and directories below the home-directory. All other filesystems are indicated as omitted. This can be changed by deleting the respective entries. Unfortunately it is not possible to switch baloo off through systemsettings. If baloo is not wanted on the system, then the package “baloo-file” needs to be removed to prevent files being indexed. The package “baloo-pim” (only present when kdepim is installed) can be removed if no search capabilities are required for kmail.

The only search client currently available for baloo, is the package called milou. Milou can be placed in the panel for easy access and the usage is quite simple. The search term is indicated and search results are shown for files, emails, etc. In the Milou settings, the categories from which results are shown can be selected. Milou can NOT be placed in the systray, as that this would cause the plasma desktop to crash upon login.

Tags on files are no longer stored inside the database, but stored in the extended file attributes (xattr), which are stored in separate files on the filesystem.

Known issues with KDE 4.13

  • The initial indexing can be heavy on I/O especially if there are large text files: either one waits till the indexing is complete (this step is done only once), or the folder containing such files is excluded using System Settings.
  • Some data will be lost during the migration: in particular, emails will have to be re-indexed, and file<->activity associations, if used, will not be preserved.
  • Milou causes the Plasma-desktop to crash if it is placed in the systray !!

KDE:Unstable:SC is moving forward

For some time now, the KDE:Unstable:SC repository for openSUSE did not offer any new snapshot due to the work that was going into getting KDE 4.10 into the upcoming openSUSE 12.3 release. Now that the latest KDE 4.10 Release Candidate (RC2) was placed into the correct repositories, I found some time again to update the KDE:Unstable:SC to a new snapshot from KDE git-master (KDE 4.11). Of course at this moment not many changes are happening in git-master due to the polishing of the KDE 4.10 release (beginning of February). 

Happy Testing…..

Release of openSUSE 12.2 (Plymouth)

IopenSUSE 12.2 got released some days ago and it seems that the plymouth integration is received very well. Even the openSUSE theme got good comments and is seen as sophisticated. This to my big surprise. 🙂  But i am very happy about it as that it proofs that we all did a good job. Unfortunately it seems that plymouth in combinztion with NVIDIA chipset can sometimes cause some unpleasant surprises. But lets hope we cn sort this out with the next release.

As that the pressure ix off again, i started to work on updates of KDE:Unstable:SC again. Yesterday kdegames was moved from svn to git and split out in seperate repositories. So a lot of new packages have to be created. Hopefully i can finish this soon, so that i can create a new snapshot this coming weekend.

Also Chromium saw a big chance recently. A couple of builds ago we noticed that chromium started to behave rathar crashy. Investigations showed that the our attempt to build with as much system libraries as possible failed. The chromium developers seemed to hsve r3ached the point where the system libraries are no longer compatible with the ones shipped with the chromium source. So as of two build, Chromium is now switched to utilize its full sourcecode. This resolved the issues and also the wotk required in keeping the opensuse patches up to date.

I know that for quite some time the KDE:Unstable:SC repo didn’t contain any recent snapshots. The repo was used to test the 4.8.0 tarballs and since then no more updates took place. 

However since today that has changed. As of now KDE:Unstable:SC contains a very recent snapshot of the KDE SC 4.9 and the packages got published. As always the target is to provide weekly snapshots of the KDE SC 4.9 and other packages. 
At this moment the kdemultimedia packages (juk, kmix, kio_audiocd, etc) are still on the 4.8.2 level as that the main KDE repository is moved from SVN to GIT. As soon as this has been completed, the packages in KDE:Unstable:SC will be updated with the next possible snapshot. 
I have been running snapshots of KDE 4.9 and I have to say that the stability is quite good. Most of the changes are the rewrite of plasmoids, etc to the new QML language. 

A little warning to those that have switched over to the KDE:Unstable:SC repo. The target is that either tonight or tomorrow a new Trunk snapshot will be loaded in this repo. That would mean that the Unstable becomes unstable again 🙂 

I have already been building a number of snapshots based on the opened KDE 4.7 trunk and have to admit that things are still looking very stable and even kdebindings is compiling well 🙂 
But this might of course change from the moment that KDE 4.6 has been released and the focus shifts to the newer 4.7 release. 
I will keep you posted on the developments around this repository, but this would be the moment to switch over to KDE:Distro:Factory if you want to get the RC1, RC2 and KDE 4.6 final version for your openSUSE system.  Currently it contains RC1, but this would change in the next few days once RC2 is released. 

Are you using the openSUSE KDE 4.6 Beta 2 packages and you would like to try a newer version ? Then for the time being you could switch over to the KDE:Unstable:SC repository. 

About 2 weeks ago, I copied the official KDE 4.6 Beta 2 packages over from the KDE:Distro:Factory repository to the KDE:Unstable:SC repository. This has two effects, namely:
1)   People using 4.6 Beta 2, can easily update to a slightly newer version to see if bugs have been resolved, without loosing important patches that are openSUSE specific. 
2)   It gives us, the openSUSE KDE team the change to easier and faster adopt to a newer release (e.g. RC1, RC2, etc), as that all patches are matches on a weekly basis to the newer source code. 
If you decide to switch repository, then make sure that you keep an eye on this blog, as that on a certain moment the KDE:Unstable:SC will switch to very unstable snapshots of the future KDE 4.7. I will however blog here to let you know that you should switch back again repostories, before I will publish the first KDE 4.7 snapshot. 
Feel free to contact me over email or on IRC (tittiatcoke) if you have any questions about this. 
So far KDE 4.6 has been a very stable release and also KDEPIM 4.6 is looking better. Let’s hope that the last glitches are also resolved, before KDE 4.6 is released. 

I guess that maybe some people were wondering how come that it was so silence around the Unstable repository for openSUSE. There are two reasons for it. First one is that I have been on holidays and I promised my family that I would stay away from a computer as much as possible. Secondly in August the KDE repositories were changes and optimized. This meant not only a new name and/or location, but also we had a good look at what was provided by each repo.

For the KDE4:Unstable repo it was agreed that the new repo name would be KDE:Unstable:SC and that it should only provide the standard KDE:SC packages with the build-required libraries. This means that application like Amarok, choqok, konversation, etc are no longer provided through this KDE:Unstable:SC repository. SVN snapshot versions of these applications can be found in the new playground (KDE:Unstable:Playground) repo or released version can be retrieved directly from either the openSUSE:Factory repository or in case of an older distribution from the KDE:UpdatedApps repository.

After the release of openSUSE 11.3, KDE:Unstable:SC was moved to the newer snapshots of the upcoming KDE 4.6 release. Unfortunately with the new 4.6svn tarballs, the python kdebindings is no longer building and therefore the kdegames package is no longer building the kajongg game. So far this has been the only victim 🙂 As that KDE:Unstable:SC is only offering a weekly snapshot and that some people would like to keep more up-to-date with the changes of the KDEPIM module, I decided to create a new repository that would hold daily updates of just the three KDEPIM related packages.

Hopefully i will blog more frequently in the future 🙂

For those interested in the right places of all the new repositories :


KDE:Unstable:Playground<openSUSE-KDE version>


Stay tuned !!

Since yesterday evening the openSUSE KDE4:Unstable repositories contains the KDE SC 4.5 rc1 packages. Also the special repository that contains KDEPIM 4.5 snapshots, was updated to a version that seems to work pretty well.

I am not using IMAP, so I can’t comment on it’s status. But the POP accounts are working very well and also filtering is active. At least it allowed me to move away again from Thunderbird to this Kmail v2 solution. A very good job done by the KDEPIM developers!!

Another week, another snapshot 🙂

As of this morning the KDE4:Unstable repository for openSUSE contains a newer snapshot (4.4.86). As that openSUSE:Factory now contains Qt4 4.6.3, all targets for KDE4:Unstable are build with the same Qt4 version, which brings a lot of stability and bugfixes.

A few people already indicated that they find the latest version becoming more responsive and that things seems much faster than previous versions.

I would say grab the new version and try it yourself.


As of today the openSUSE KDE4:Unstable repositories are now offering the new KDE SC 4.5 Beta 2 packages for 11.1, 11.2 and Factory. So come and get them !! The new beta also has an update on the polkit-kde-1 package which resolves the segmentation fault when logging off.

Besides the KDE SC 4.5 Beta 2, the repositories are also offering the updates to konversation 1.3, digikam 1.3.0 and kipi-plugins 1.3.0.

New in the repositories is the verktyg package for kdevelop (See also this blog about verktyg). Based on the verktyg package, the kdevelop and kdevplatform packages have been updated to the latest git versions. New is also the kdevcpptools package which is a supporting package for verktyg. At the moment verktyg is not tested yet !!