Version: (using KDE KDE 3.4.92) Installed from: Ubuntu Packages Compiler: gcc-4.0.2 OS: Linux I installed the ubuntu packages for kde3.5_beta2. Since then I get an error when starting akregator. It does not find it's storage plugin to archieve the messages.
Have you run kbuildsycoca before starting akregator? If in doubt, run it and restart KDE.
Isn't kbuildsyscoca run when starting kde? Well, I ran it as my user logged out, logged in again and still the same. kbuildsyscoca gave me this error message: kio (KSycoca): ERROR: No database available! Is this a part of kbuildsycoca or just another error?
That kbuildsycoca message looks suspicious, but I can't tell what it means right now. Could you try and create a "fresh" user and see if it makes a difference? I have seen problems like this only with "mixed" setups, e.g. KDE 3.4 with kdepim 3.5.
It's the same with a "fresh" user. When I installed the new version of kde I just added the new package source and did a dist-upgrade. There should be no old files.
The Akregator package for KDE 3.5b2 is completely broken, shared files of metakit backend do not exist (libakregator_mk4storage_plugin.* in /usr/lib/kde3). No Akregator problem, just packaging problem, I'll send it to Kubuntu devs.
http://bugzilla.ubuntu.com/show_bug.cgi?id=18266
The Akregator package for KDE3.5beta2 is effectively broken in kubuntu, but the shared files of the metakit backend exist in the libkcal2a package, BUT not in the right places (in /usr/...), they are wrongly(??) stored in /tmp/usr/..., I just copied the missing files in the right places in the /usr/... hierarchy, and akregator is working fine without a single crash (since yesterday). I will send this comment to the kubuntu devs.
*** Bug 116206 has been marked as a duplicate of this bug. ***
Bug has been fixed as KDE 3.5 RC 1 packages are now available in Ubuntu repository.