Skip to content

Wednesday, 17 October 2018

Also available in Italian, Spanish and Taiwanese Mandarin.

Hi everyone!

This time we have been a bit late, as many of our contributors were busy over the last couple of months, but we hope we can soon get back to normal delivery times. :blush:

Better late than never though, so we are happy to inform you that on your next system upgrade you will receive newer versions of KDE’s Plasma, Applications and Frameworks, in addition to updates to important packages such as the linux kernel and systemd. The latest Plasma 5.14 series should follow soon.

Please have in mind that we have removed the nvidia-304xx package from Chakra’s repositories because it is no longer compatible with new kernel releases. If you are using nvidia-304xx on your system, you should either install and use the linux-lts kernel and the corresponding nvidia-304xx-lts package, or switch to the free nouveau driver.

For more details and the full changelogs on KDE’s software releases, you can read the official announcements:


Noteworthy package updates include:


  • curl 7.61.1
  • gcc 8.2.0
  • linux 4.18.12
  • linux-lts 4.4.152
  • nvidia 410.57
  • nvidia-390xx 390.87
  • openssh 7.8p1
  • systemd 239.0
  • vlc 3.0.4


  • wine 3.18

It should be safe to answer yes to any replacement question by the package manager application. If in doubt or if you face another issue in relation to this update, please ask or report it below.

Most of our mirrors take 12-24 hours to synchronize with the central repositories on the origin server. Use the mirror status web page to see when your mirror of choice last synchronized.


24 posts - 15 participants

Read full topic

We will be holding a Bug Day on October 20th, 2018, focusing on Konsole. Join at any time, the event will be occurring all day long!

This is a great opportunity for anyone, especially non-developers to get involved!

  1. Mascot_konqi-support-bughunt.pngCheck out our Bug Triaging guide for a primer on how to go about confirming and triaging bugs.
  2. Log into KDE Phabricator and join the Bugsquad!
  3. Join the #kde-bugs IRC channel on Freenode to chat with us in real-time as we go through the list.
  4. Open the shared Etherpad for this event (use your KDE Identity login) to select your block of bugs and cross them off.

If you need any help, contact me!

Monday, 15 October 2018

It’s time for another digiKam Recipes update. The most visible change in the latest revision is the new book cover. All screenshots were also updated to reflect changes in the current version of digiKam. In addition to the visual tweaks, the latest revision features new content. Continue reading…
Got a NAS? Still store your photo library and digiKam databases on a local machine? It’s time to take your digiKam setup to the next level by moving your photo library to the NAS and switching to the MariaDB (or MySQL) database backend. This allows you to access your photo library from any machine on the same network as well as keep your photo library safe thanks to the fact that storage on most NAS appliances is usually configured as RAID.

Sunday, 14 October 2018

We are pleased to announce the new release 5.4 of KPhotoAlbum, the KDE photo management software!

Please consider that we dropped support for older Qt versions with this release. You will need at least Qt 5.8 to build KPA now.

Another notable change is that FreeBSD is now also a supported platform of KPA.

New developer

We're especially delighted to welcome a new KPA developer: Robert Krawitz. He supplied us with meaningful patches for quite some time now, and finally decided to really step in now. For v5.4, he contributed and changed a lot of code touching complicated parts of KPA, mostly, the changes were about optimizing code, speeding it up and removing unneeded or obsolete parts.

Kudos for this! We hope to have another long-term developer with Robert now. Welcome to the team :-)

A selection of improvements and speedups in version 5.4 follows:

  • Insert Exif data for each loaded image as it's loaded, but within a transaction.
  • Elide unnecessary MD5 computations.
  • Reduce I/O wait time of image loader by introducing a scout thread.
  • Improve I/O efficiency for MD5 calculation.
  • Fetch Exif data only once during load.
  • Improve efficiency of loading previews from RAW images.
  • Ignore more sidecar files to improve performance (.xmp, .pp3, and .pto).
  • Improve thumbnail generation speed and efficiency.
  • Overlap thumbnail create with image load.
  • Generate new thumbnails for moved images detected during load.
  • Speedup startup 10-15% by eliding unnecessary category creation.

L10N rework

Big thanks also go to Antoni Bella Pérez, who put a lot of work on reworking the localizable stings in KPA, fixed a lot of errors, added contexts and made the whole thing follow KDE's I18N guidelines better.

Thanks to everybody involved

Here's an alphabetically sorted list of people who contributed to this release.

  • Antoni Bella Pérez
  • A. Wilcox
  • Christophe Giboudeaux
  • Johannes Zarl-Zierl
  • Pino Toscano
  • Robert Krawitz
  • Tobias Leupold
  • Yuri Chornoivan

Thanks for all the work!

— Tobias

It’s been rather quiet when it comes to accessibility in KDE land for a while. But I’m very happy to see some movement and fresh energy, moving in a good direction.

If you’re curious about making our software available to more users, improving it for everyone (for example keyboard usability), now is the time to join. We are talking on the accessibility mailing list. It’s still to early to say what the exact plan will look like, but there will be progress. Thanks to the last Randa meeting, we reached the point where a few things in Plasma do work with a screen reader, enough to let a few brave souls experiment with it. Now we’ll have to structure what needs improvements, I could imaging defining some workflows. Once we have broken down the big goal of making Plasma a joy to use with a screen reader, we’ll have to make sure of a few things for each sub goal:

  • Keyboard navigation needs to work – being blind, using a mouse is often pointless, since you won’t see the pointer. It’s very important that we can do everything with the keyboard. This is of course good for everyone, we all win.
  • The screen reader needs to know what to present to the user – we need to make sure that buttons that only show an icon have an alternative description for example. Some work has been done in this direction, but without user testing, it won’t be polished or even complete.
  • Performance fixes in the accessibility stack – this needs some investigation, some of the implementation in Qt may not be in agreement with what Orca expects.
We will try to coordinate the work starting on the Plasma Accessibility Phabricator board.
I think we really need someone to take on the role of coordinator and help move this forward, listening to users what’s most important and getting developers to spend a little time fixing things. This is really something anyone can help with, and I think we already have some people interested on the list.

Friday, 12 October 2018

It’s been two months already since Akademy 2018 took place and unfortunately due to life changes I’ve only just now managed to sit down and write something about it. Perhaps one reason that this took me so long is that I needed this time to process and absorb all the new information and experiences I was exposed to during my time in Vienna. I left Akademy with so much new information, a long list of to-dos, feeling overwhelmed but at the same time extremely motivated to start working on things.

Friday, 21 August 2015

Update 1: Google Play still not has the newest version, but it is incomming in the following days
Update 2: There is an open beta version now, you can get it from here from Google Play.

Marble Maps has the following features:
  • Wondering around on the map
    • You can move the map with one finger by dragging the map with it
    • It will increase the zoom if you touch double times fast to the map
    • You can also zoom with two fingers (only supported on multitouch devices)
  • Handling your position
    • You can check your position on the map
    • You can check the distance and direction to your position when your position is not visible
    • You can center the view to your position
  • Routing
    • You can plan routes via interactive placemarks, you have to search for something and after that, you can use the result as a waypoint
    • Also, you can modify the route instead of the interactive waypoints with the route editor which is available from the menu

    • To get the routing instructions, visit the menu too
    • You can select from three routing profile: with car, with bike or as a pedestrian
  • Navigation
    • You can navigate on the route what you have planned previously, or you can also navigate to a single destination
    • Marble Maps shows your position on the route with a different icon
    • It provides turn-by-turn based navigation
    • It uses the Text To Speech interface of the Android system to provide voice instructions. To use it, please install it from Google Play
    • It shows the next instruction and its distance too
    • The current speed and the distance to the destination is also visible 

Some techincal background:
Marble's base source code in this summer has become Android compatible. If you want an Android app can be built on the top of it. Any map can be loaded in, and all of the projections are available. It supports some plugins too.

And finally my personal experience about the summer:
I liked to work on this project very much because I have learned a lot of new things, like coding technics, I have got closer to QML and I also have had a deeper insight on how Android applications work. It was also good to work with the people of the community. I would like to thank to everybody who helped me this summer, especially to Dennis Nienhüser and to Torsten Rahn. Without them Marbe on Android would be still a dream.

Thank you Google for this fantastic opportunity!

But the story is not ending here, so stay tuned...