Language Selection

English French German Italian Portuguese Spanish

KDE 4.4 Mail Misunderstanding Explained & Akregator Surprize

Filed under
Linux

I've gotten quite a few responses to my quickie look at KDE 4.4 under Mandriva written for this week's Distrowatch Weekly. One of which came from Aaron J. Seigo himself. I thought I might share some of what he said since several people expressed similar concerns on the topic here in comments. I also found one really super-duper neato new feature in Akegator in 4.4 that deserves a mention.

First to all, that wasn't meant to be a thorough review of KDE 4.4. I just wanted to talk about how easy it was to upgrade Mandriva and to install the KDE 4.4 packages and perhaps mention a few observations.

But one concern that several people besides myself have mentioned about KDE 4.4 PIM here on Tuxmachines was our understanding that our emails used in KDE PIM will be converted from our maildir format to database entries. This would make testing various distributions a bit more difficult. I know a little MySQL, but I really didn't want to be dumping and restoring a database every time I changed distributions.

But Seigo explains that our mail will not be converted and stored in a database. An index of our mail will be made and stored in a database table so that other applications could make use of it. Apparently, allowing for opening and accessing the mail in its current directory and format if need be - for example, as in a plasma widget on desktop monitoring for new mails. At least that's how I understood his explanation.

Well, instead of interpreting, I'm sure it would be alright to just post his exact words:

Actually, Akonadi doesn't change storage format (that wouldn't be a good move, really) but it centralizes access to the storage as well as provides uniform indexing. Right now, indexing systems aren't shared between mail/calendar/contact systems anyways, and Nepomuk allows the indexing to be shared between all desktop apps that use it. Akonadi itself provides access to the mails on disk so that it's safe for both, say, KMail and and a Plasma widget to be displaying the contents of the at the same time. So instead of being a heavy or "lock-in" style database, it's simply an access mechanism to storage formats that you and I are already (and will continue to) use.

I know this takes a load off my mind as I hope it does the others who expressed concern as well.

---

Now for the super-duper neato new feature in Akregator:

Akregator used to display polls and such as plain text, but with 4.3.2 polls rendered in radio-button or clickable format. That was kinda nice. But today I discovered something even better.

For Webmasters/bloggers/whoever that allow such, videos can now be watched right from Akregator. I don't know any real details, if only certain formats are supported and such, but I'm almost thinking they'd have to be oggs. I'm not sure if Flash videos would work as I disable all such in Konqueror/KDE. I'll check next time I see where someone embeds one in a feed.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: akonadi problems

On my experimental box, I'm running Mandriva's development version called Cooker (currently in Alpha state). When Cooker KDE packages were updated to KDE 4.40, akonadi wouldn't load, so kmail would terminate. Irritating. Started looking on the net, and in logs. Turned out the akonadi MySQL database config was incompatible with the MySQL packages in Cooker.

Some small changes in the akonadi mysql config file got it working.

Oh well, such is the life with alpha stuff.

Wish KDE would allow kmail to run without akonadi, for the time being.

re: akonadi problems

oh no. Another issue to be wary of. That won't be the only occurrence of similar in the coming months I'm afraid.

Yes, there should be some choice in the matter. A lot of folks would rather not have to have a database installed on their desktop.

Issues of space, resources, unknown future of mysql... that database indexing should be an option one can opt out of.

More in Tux Machines

today's howtos

Graphics: VC4 and AMDVLK Driver

  • VC4 display, VC5 kernel submitted
    For VC5, I renamed the kernel driver to “v3d” and submitted it to the kernel. Daniel Vetter came back right away with a bunch of useful feedback, and next week I’m resolving that feedback and continuing to work on the GMP support. On the vc4 front, I did the investigation of the HDL to determine that the OLED matrix applies before the gamma tables, so we can expose it in the DRM for Android’s color correction. Stefan was also interested in reworking his fencing patches to use syncobjs, so hopefully we can merge those and get DRM HWC support in mainline soon. I also pushed Gustavo’s patch for using the new core DRM infrastructure for async cursor updates. This doesn’t simplify our code much yet, but Boris has a series he’s working on that gets rid of a lot of custom vc4 display code by switching more code over to the new async support.
  • V3D DRM Driver Revised As It Works To Get Into The Mainline Kernel
    Eric Anholt of Broadcom has sent out his revised patches for the "V3D" DRM driver, which up until last week was known as the VC5 DRM driver. As explained last week, the VC5 driver components are being renamed to V3D since it ends up supporting more than just VC5 with Broadcom VC6 hardware already being supported too. Eric is making preparations to get this VideoCore driver into the mainline Linux kernel and he will then also rename the VC5 Gallium3D driver to V3D Gallium3D.
  • AMDVLK Driver Gets Fixed For Rise of the Tomb Raider Using Application Profiles
    With last week's release of Rise of the Tomb Raider on Linux ported by Feral Interactive, when it came to Radeon GPU support for this Vulkan-only Linux game port the Mesa RADV driver was supported while the official AMDVLK driver would lead to GPU hangs. That's now been fixed. With the latest AMDVLK/XGL source code as of today, the GPU hang issue for Rise of the Tomb Raider should now be resolved.

AMD Ryzen 7 2700X Linux Performance Boosted By Updated BIOS/AGESA

With last week's initial launch-day Linux benchmarks of the Ryzen 5 2600X / Ryzen 7 2700X some found the Linux performance to be lower than Windows. While the root cause is undetermined, a BIOS/AGESA update does appear to help the Linux performance significantly at least with the motherboard where I've been doing most of my tests with the Ryzen 7 2700X. Here are the latest benchmark numbers. Read more

GNU: The GNU C Library 2.28 and Guix on Android

  • Glibc 2.28 Upstream Will Build/Run Cleanly On GNU Hurd
    While Linux distributions are still migrating to Glibc 2.27, in the two months since the release changes have continued building up for what will eventually become the GNU C Library 2.28. The Glibc 2.28 work queued thus far isn't nearly as exciting as all the performance optimizations and more introduced with Glibc 2.27, but it's a start. Most notable at this point for Glibc 2.28 is that it will now build and run cleanly on GNU/Hurd without requiring any out-of-tree patches. There has been a ton of Hurd-related commits to Glibc over the past month.
  • Guix on Android!
    Last year I thought to myself: since my phone is just a computer running an operating system called Android (or Replicant!), and that Android is based on a Linux kernel, it's just another foreign distribution I could install GNU Guix on, right? It turned out it was absolutely the case. Today I was reminded on IRC of my attempt last year at installing GNU Guix on my phone. Hence this blog post. I'll try to give you all the knowledge and commands required to install it on your own Android device.
  • GNU Guix Wrangled To Run On Android
    The GNU Guix transactional package manager can be made to run on Android smartphones/tablets, but not without lots of hoops to jump through first.