New KDE 4.2 Updates

Today, as I issued ‘sudo yum update’, I was greeted with a flurry of new updates for KDE 4.2. These are the following:

=====================================================================
Package Arch Version Repository Size
=====================================================================
Updating:
PyKDE4 x86_64 4.2.1-1.fc10 kde-testing 4.8 M
PyQt4 x86_64 4.4.4-5.fc10 kde-testing 3.2 M
kdeaccessibility x86_64 1:4.2.1-1.fc10 kde-testing 6.6 M
kdeartwork x86_64 4.2.1-1.fc10 kde-testing 14 M
kdebase x86_64 6:4.2.1-2.fc10 kde-testing 5.7 M
kdebase-libs x86_64 6:4.2.1-2.fc10 kde-testing 272 k
kdebase-runtime x86_64 4.2.1-2.fc10 kde-testing 6.6 M
kdebase-runtime-libs x86_64 4.2.1-2.fc10 kde-testing 1.3 M
kdebase-workspace x86_64 4.2.1-3.fc10 kde-testing 13 M
kdebase-workspace-libs x86_64 4.2.1-3.fc10 kde-testing 734 k
kdeedu x86_64 4.2.1-1.fc10 kde-testing 25 M
kdeedu-kstars x86_64 4.2.1-1.fc10 kde-testing 10 M
kdeedu-libs x86_64 4.2.1-1.fc10 kde-testing 345 k
kdeedu-marble x86_64 4.2.1-1.fc10 kde-testing 18 M
kdeedu-math x86_64 4.2.1-1.fc10 kde-testing 3.5 M
kdegames x86_64 6:4.2.1-1.fc10 kde-testing 32 M
kdegames-libs x86_64 6:4.2.1-1.fc10 kde-testing 1.3 M
kdegraphics x86_64 7:4.2.1-1.fc10 kde-testing 2.5 M
kdegraphics-libs x86_64 7:4.2.1-1.fc10 kde-testing 1.8 M
kdelibs x86_64 6:4.2.1-4.fc10 kde-testing 13 M
kdelibs-common x86_64 6:4.2.1-4.fc10 kde-testing 361 k
kdemultimedia x86_64 6:4.2.1-1.fc10 kde-testing 1.7 M
kdemultimedia-libs x86_64 6:4.2.1-1.fc10 kde-testing 308 k
kdenetwork x86_64 7:4.2.1-1.fc10 kde-testing 8.1 M
kdenetwork-libs x86_64 7:4.2.1-1.fc10 kde-testing 1.7 M
kdepim x86_64 6:4.2.1-2.fc10 kde-testing 11 M
kdepim-libs x86_64 6:4.2.1-2.fc10 kde-testing 7.3 M
kdepimlibs x86_64 4.2.1-2.fc10.1 kde-testing 1.9 M
kdeplasma-addons x86_64 4.2.1-1.fc10 kde-testing 5.0 M
kdesdk x86_64 4.2.1-1.fc10 kde-testing 7.2 M
kdesdk-libs x86_64 4.2.1-1.fc10 kde-testing 283 k
kdesdk-utils x86_64 4.2.1-1.fc10 kde-testing 258 k
kdeutils x86_64 6:4.2.1-1.fc10 kde-testing 2.8 M
ksysguardd x86_64 4.2.1-3.fc10 kde-testing 72 k
libX11 i386 1.1.5-1.fc10 updates-testing 830 k
libX11 x86_64 1.1.5-1.fc10 updates-testing 832 k
oxygen-icon-theme noarch 4.2.1-2.fc10 kde-testing 15 M
phonon x86_64 4.3.1-2.fc10 kde-testing 153 k
phonon-backend-gstreamer
x86_64 4.3.1-2.fc10 kde-testing 108 k
phonon-backend-xine x86_64 4.3.1-2.fc10 kde-testing 165 k
qt x86_64 1:4.4.3-15.fc10 kde-testing 3.5 M
qt-mysql x86_64 1:4.4.3-15.fc10 kde-testing 47 k
qt-x11 x86_64 1:4.4.3-15.fc10 kde-testing 13 M
Installing for dependencies:
kdepimlibs-akonadi x86_64 4.2.1-2.fc10.1 kde-testing 331 k
kio_sysinfo x86_64 20090216-2.fc10 kde-testing 353 k

Transaction Summary
=====================================================================
Install 2 Package(s)
Update 43 Package(s)
Remove 0 Package(s)

Total download size: 246 M

The dilemma with all of this is that I just got KDE back up and running. I had the problem where Akonadi wasn’t running! Consequently, Kontact (my calendar/todo lifeblood) would not launch without error. I completely lots a ton of my planned todos and planned calendar events–when I could get it working.

This whole dilemma almost prompted a permanent move from my beloved Thunderbird/Kontact communication and planning combo to Evolution, the Gnome rival to MS Outlook (complete with Exchange server components). However, Kontact is a much better calendar/todo application (to me!) complete with good color and organization schemes. Evolution seemed unintuitive and required multiple mouse-clicks to get around.

In the end, a site (which unfortunately I cannot cite because I didn’t bookmark it before restarting KDE) prompted me to backup my .kde directory and then delete the .kde directory entirely (rm -rf .kde)! This worked. I only had to change some settings (which implies that most of my personalizations are not stored in .kde).

Now, I sit here updating this working KDE 4.2.0 configuration with literally tons of new downloads from the KDE-TESTING repo because that’s where I can get x86_64 packages for Fedora 10. I am wondering if this was a good move. Time will tell.

Leave a Reply