October 26, 2016


I did a lot of work for breeze icons and l think it fits the kde desktop, gnome core and libreoffice very well.

But kde mean community, customization, open for 3rd party. So I would like to help icon designers to ship there icon sets for kde or libreoffice. I don’t want to start a new icon set. I’d like to help open source designers to ship there awesome work for kde.

Are you an icon designer and need help? Are you a user and want to have a better integration of your favorite icon set? Are you an app developer and your app wasn’t supported with breeze icons.

Leave a comment, for a better open source experience.

We are happy to announce the release of Qt Creator 4.2 Beta.

Qt SCXML Editor

Flat Dark Theme - Qt Creator 4.1

Qt SCXML is a new module in Qt that allows you to create state machines from State Chart XML and embed them into Qt C++ and Qt Quick applications (Overview). It was released as Technical Preview in Qt 5.7 and will be released fully supported with Qt 5.8.

Qt Creator 4.2 now supplements the module by offering a graphical editor for SCXML (experimental). It features editing states and sub-states, transitions, events, and all kinds of properties. The editor is experimental and the plugin is not loaded by default. Turn it on in Help > About Plugins (Qt Creator > About Plugins on macOS) to try it.

Projects Mode

We reworked how you select the project and it’s diverse settings in Projects mode. Instead of nested tabs, you now select the project from a dropdown, and the settings that you want to edit from a tree that shows all available kits and other categories, making for a much cleaner UI. Enabling use of a kit for a project is now easily done by clicking the entry in the tree. Please provide feedback on any remaining issues through our bug tracker.

Qt Quick Designer

Qt Quick Designer has received many smaller features in this release. In the connections editor there is a new section for managing the imports and property definitions that are necessary for using C++ backend objects (documentation). Also support for padding (Qt Quick 2.6) was added, and you can now edit the when condition of states, and the diverse font properties of text items.

Other Additions and Improvements

When profiling your QML code you now have the option to show memory usage and allocations as flame graphs as well.

We added Tools > Diff > Diff Current File and Diff Open Files for showing a local diff of the modifications of files in Qt Creator with respect to their versions on disk.

CMake integration has added support for platforms and toolsets, and for predefined options for properties.

There were many more changes, which are described in more detail in our change log.

Get Qt Creator 4.2 Beta

The opensource version is available on the Qt download page, and you find commercially licensed packages on the Qt Account Portal. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on chat.freenode.net, and on the Qt Creator mailing list.

The post Qt Creator 4.2 Beta released appeared first on Qt Blog.

Yesterday I conducted my talk at the OpenStack Summit in Barcelona. You can find the presentation here: "Vanilla or Distributions: How Do They Differentiate?" and the video from the session on the OpenStack Foundation youtube channel

Any feedback would be welcome, please don't forget to rate the presentation in the OpenStack Foundation Summit app.

Nos costó arrancar este año. Tuvimos un invierno duro pero nos hemos puesto las pilas desde el verano para que la segunda temporada de podcast llegue a un número aceptable de ellos. De esta forma, ya llevamos 5 episodios esta segunda temporada, quedando solo a dos de igualar a la primera. No obstante, tenemos un problema, no sabemos que temas os interesan más. Así que os pedimos colaboración: ayúdanos a decidir el tema del próximo podcast de KDE España que grabaremos en el mes de noviembre.

Ayúdanos a decidir el tema del próximo podcast de KDE España

Ayúdanos a decidir el tema del próximo podcast de KDE EspañaSi no hay inconveniente, el próximo 15 de noviembre tendremos el gusto de reunirnos algunos simpatizantes del proyecto KDE para realizar el sexto episodio de la segunda temporada de los podcast de KDE España. 

No obstante, en esta ocasión no puedo avanzar el tema ya que no lo tenemos decidido. Así porque queremos que seáis vosotros los que nos ayudéis a decidir participando en una encuesta. Así que para participar os animo a hacer clic en este enlace o directamente en el tweet inferior.

Como veis en esta ocasión no nos decidimos entre hablar de cosas técnicas (y muy importantes) o cosas más orientadas a usuarios (y también muy importantes). ¡Ayudadnos! Tenéis hasta este sábado 29 de octubre a las 11:30  para votar.

Los podcast de KDE España

Ayúdanos a decidir el temaEn un afán de acercarnos más a todos los simpatizantes de KDE hace un tiempo que empezamos a realizar podcast. En ellos varios miembros de la Comunidad KDE de España nos reunimos para hablar un poco de los diversos proyectos.

Hemos hablado de muchos temas como por ejemplo Akademy, KDE Connect, Plasma Mobile, el aniversario de KDE, distribuciones, blogs, etc.

Podéis seguirnos en  el canal de Youtube de KDE España o en Ivoox, donde estamos subiendo poco a poco los audios emitidos. Esperamos que os gusten.

October 25, 2016

From August 31th to September 10th I was em Berlin attending two amazing conferences: QtCon and Akademy.

QtCon brought together five communities to host their respective conferences at a same time and place, creating one big and diverse conference. Those communities were Qt, KDAB, KDE (celebrating 20th birthday), VLC and FSFE (both celebrating 15th birthday).


Main conference hall of QtCon at bcc

That diversity of themes was a very interesting characteristic of QtCon. I really appreciated see presentations of Qt and KDAB people, and I was surprised about topics related with VLC community. The strong technical aspects of trends like Qt in mobile, Qt in IoT (including autonomous cars), the future of Qt, Qt + Python, contributing to Qt, and more, called my attention during the conference.

On VLC I was surprised with the size of the community. I never imagined VLC had too much developers. In fact, I never imagined VideoLAN is in fact an umbrella of a lot of projects related with multimedia, like codecs, streaming tools, VLC ports to specific devices (including cars through Android Auto), and more. Yes, I really appreciated to find these persons and watch their presentations.

I was waiting for the VLC 3.0 release during QtCon, but unfortunately it did not happen. Of course the team is improving this new release and when it is finished I will have a VLC to use together with my Chromecast, so, keep this great work coneheads!

FSFE presentations were interesting as well. In Brazil there are several talks about political and philosophical aspects of free software in conferences like FISL and Latinoware. In QtCon, FSFE brought this type of presentation in an “European” style: sometimes the presentations looks like more pragmatically in their approaches. Other FSFE presentations talked about the infrastructure and organizational aspects of the foundation, a nice overview to be compared with others groups like ASL.org in Brazil.

Of course, there were a lot of amazing presentations from our gearheads. I highlight the talks about KDE history, Plasma Desktop latest news, Plasma Mobile status, KF5 on Android, the experience of Minuet in mobile world, among others.

The KDE Store announcement was really interesting and I expect it will bring more attention to the KDE ecosystem when software package bundles
(snap/flat/etc) be available in the store.

Other software called my attention was Peruse, a comic book reader. I expect developers can solve the current problems in order to release a mobile version of Peruse, so this software can reach a broad base of users of these platforms.

After the end of QtCon, Akademy had place in TU Berlin, in a very beautiful and comfortable campus. This phase of the conference was full of technical sessions and discussions, hacking, and fun.

I attended  to the Flatpack, Appstream, and Snapcraft BoFs. There were a lot of advanced technical discussions on those themes. Every Akademy I feel very impressed with the advanced level of the technical discussions performed by our hackers in KDE community. Really guys, you rocks!

The Snapcraft BoF was a tutorial about how to use that technology to create crossdistro bundle packages. That was interesting and I would like to test more and give a look in Flatpack in order to select something to create packages for Cantor.

Unfortunately I missed the BoF on Kube. I am very interested in an alternative PIM project for KDE, focused in E-Mail/Contacts/Calendar and more economic in computational resource demand. I am keeping my eyes and expectations on this project.

The others days basically I spent my time working on Cantor and having talk with our worldwide KDE fellows about several topics like KDE Edu, improvements in our Jabber/XMPP infrastructure, KDE 20th years, Plasma in small-size computers (thanks sebas for the Odroid-C1+ device 😉 ) WikiToLearn (could be interesting a way to import/export Cantor worksheets to/from WikiToLearn?), and of course, beers and Germany food.

And what about Berlin? It was my second time in the city, and like the previous one I was excited with the multicultural atmosphere, the food (<3 pork <3) and beers. We were in Kreuzberg, a hipster district in the city, so we could visit some bars and expat restaurants there. The QtCon+Akademy had interesting events as well, like the FSFE celebration in c-base and the Akademy daytrip in Peacock Island.

So, I would like to say thank you for KDE e.V. for funding my attendance in the events, thank you Petra for help us with the hostel, and thank your for all the volunteers for work hard and make this Akademy edition a real celebration of KDE community.


Some Brazilians in QtCon/Akademy 2016: KDHelio, Lamarque, Sandro, João, Aracele, Filipe (me)

New mobile IMG update,

  • Updated packages
  • Newer libwayland then one available in Ubuntu repositories
  • Experimental activity switcher applet

You can flash using instructions at https://plasma-mobile.org/nexus-5/

Today the OpenStack Summit started in Barcelona, Spain, with the keynotes.

Looking forward to my talk later today: Vanilla or Distributions: How Do They Differentiate? and a interesting summit the next days.
Con motivo de los 20 años de KDE la Comunidad de KDE España ha decidido mostrar su lado más humano y mostrar un poco el lado más personal de sus integrantes. Por ello muchos de ellos han  participado en la serie de entradas que he titulado “20 entrevistas para 20 años de KDE” en las que no solo hablarán de su relación con el proyecto sino que también nos mostrarán su lado más humano. Empieza la serie, como no podía ser de otra forma, el actual presidente de KDE España, Antonio Larrosa, y si todo va según lo previsto tendrá una periocidad semanal. De esta forma tendremos serie para casi medio año. Espero que os guste tanto como a mi realizarlas y maquetarlas.

20 entrevistas para 20 años de KDE (I): Antonio Larrosa

Hola, en primer lugar quisiera agradecerte tu tiempo. Seguro que tus palabras serán fuente de inspiración para otros muchos.
Para empezar me gustaría que te presentaras tu mismo:
20 entrevistas para los 20 años de KDE (I)

Antonio Larrosa posando con camiseta de su distribución favorita: openSUSE.

Mi nombre es Antonio Larrosa, nací en Málaga hace 38 años y soy licenciado en Matemáticas. Durante 10 años trabajé en una empresa de software privativo diseñando y desarrollado software para almacenamiento de datos a gran escala para el archivo de cadenas de TV sobre Linux, he sido profesor asociado en la Universidad de Málaga, en Informática e Ingeniería Industrial, y actualmente trabajo en SUSE en el equipo de escritorio. Soy miembro de KDE e.V., presidente de KDE España y representante de SUSE/openSUSE en el KDE Advisory Board.

Los inicios

¿Recuerdas como conociste KDE?
 Si no recuerdo mal, a principios del año 1997 creo que usaba Slackware 3.1 con un kernel 2.0, acababa de instalar Linux y un amigo de mi hermano comentó que había un grupo desarrollando un interfaz gráfica para hacer Linux más amigable. Por aquellos tiempos había unas 20 o 30 personas en KDE en todo el mundo y andaba por la versión 0.11 . Yo andaba buscando algo con lo que desarrollar aplicaciones gráficas en Linux, y me pareció perfecto así que empecé a colaborar.

¿Qué es lo que te gustó de KDE? ¿Y lo que menos?


Kmid, una de las primeras aplicaciones con las que colaboró Antonio.

 La facilidad que daba (ya en aquella época) para desarrollar aplicaciones y lo bonitas que quedaban. Aunque el paradigma de aplicación con buen aspecto ha cambiado mucho desde entonces, KDE se ha ido adaptando en todas las épocas a lo que los usuarios requieren. En aquella época no había nada que no gustara de KDE. Hay que tener en cuenta que eran otros tiempos y para desarrollar aplicaciones gráficas las alternativas eran X Athena Widgets, Motif (que tenía una licencia propietaria en aquellos años) o usar directamente llamadas a las X. Así que KDE fue una gran mejora respecto a todo lo que había.
¿Por qué decidiste empezar a colaborar KDE?
 Sobre un año antes, a principios de 1996 había hecho algunos parches para mejorar un programa de consola, playmidi, que reproducía ficheros midi a través de teclados electrónicos conectados al ordenador por un puerto MIDI y le añadí soporte para eventos de karaoke. A comienzos del verano de 1997, busqué como desarrollar una aplicación gráfica para hacer eso mismo, ya que pensé que sería mucho más intuitivo y daría más juego para funcionalidades más interesantes, así encontré KDE, empecé a desarrollar kmid y luego vi que podía ayudar en más áreas.
¿Cual es tu motivación para hacerlo y qué te aportó o te aporta?

¡Spiderman aprueba la frase!

Mi motivación inicial fue desarrollar algo que necesitaba en Linux y que no existía. Vi que había mucho código escrito y que me estaban dando permiso para leer, aprender y modificar cómo funcionaba absolutamente todo en mi ordenador, así que era un gran poder… y todo el mundo sabe que un gran poder conlleva una gran responsabilidad, así que decidí que yo también podía contribuir y dar un poco de vuelta a cambio de todo lo que me estaban dando y que otras personas por todo el planeta aprovecharan y se beneficiaran también de todo lo que yo hiciera. Tengo que admitir que la importancia de las licencias libres, la protección de las libertades de los usuarios y el acceso universal a la tecnología es algo que me llegó después pero que hoy en día no se debe olvidar en ningún caso.

Sobre lo que me ha aportado y aporta, creo que ha quedado claro que es mucho. Por concretar. podría decir que experiencia con linux y experiencia de programación en distintos lenguajes.

El momento actual


OpenSUSE, siempre presente en la vida de Antonio.

En la actualidad, ¿Colaboras con el Software Libre en general y KDE en particular?

Sí. Cuando terminé la carrera de Matemáticas empecé a trabajar para una empresa de software (privativo aunque sobre Linux) que me permitía usar KDE en mi día a día y mantenerme actualizado, pero no me daba tiempo para desarrollar nada más alla que alguna cosa puntual durante mis vacaciones. Así que bajé mucho mi nivel de colaboración (aunque fue cuando empezaron a unirse más españoles a KDE). Afortunadamente hace 3 años cambié de empresa y actualmente trabajo en SUSE donde todo lo que hago es Software Libre . En los últimos meses he preparado paquetes de Plasma 5 y KDE Applications para que los usuarios de SUSE Linux Enterprise Desktop/Server 12 puedan instalar y usar nuestro escritorio y aplicaciones . En las últimas semanas, he colaborado con desarrolladores de Plasma y openSUSE Leap 42.2 para hacer algunos cambios en sus respectivas planificaciones de forma que la nueva Leap 42.2 pueda llevar Plasma 5.8, he ayudado a empaquetarlo para Leap y he arreglado algunos bugs que me han permitido volver a hacer commits a los repositorios de KDE de forma más o menos continuada durante algunas semanas.
¿Qué aplicaciones o partes de KDE has colaborado?

Pues empecé con KMid, KPager (que ya no existe pero que fue el origen de la vista miniaturizada en el panel de las aplicaciones en cada escritorio virtual, cosa que no existía en Linux en la época) y otras, hice muchos arreglos en las librerías de KDE, mantuve durante muchos años las clases relacionadas con los temas de iconos y la carga de iconos, hice arreglos en casi todas las aplicaciones de KDE entre el 98 y el 2002/2003, hice traducciones de aplicaciones, tutoriales y páginas web, mantuve contactos con la prensa (durante años fui el “representante de KDE para España”), escribí artículos en revistas de publicación nacional, di cerca de 100 conferencias en distintos eventos a lo largo de toda España desde 1998 y he mentorizado varios proyectos de KDE en el Google Summer of Code. Además, fui el organizador de Akademy 2005, y de la Akademy-es 2014 que tuvieron lugar en Málaga, miembro de KDE e.V. desde 1999 y miembro fundador de la asociación KDE España, de la que recientemente he sido elegido presidente.

Akademy-es 2014

El gran evento de la Comunidad KDE española del 2014: Akademy-es 2014 de Málaga.

Me has convencido, me gustaría echar una mano ¿cómo crees que es la mejor manera de empezar?
 Haciendo lo que te guste hacer. ¿Te gusta programar? Puedes leer alguno de los fantásticos tutoriales de programación con KDE que hay y hacer tu propia aplicación o buscar fallos que arreglar en bugs.kde.org y ayudar a pulir más aún el escritorio. ¿Te gusta dibujar? Dibuja iconos con nuevos estilos o mejorando la intuitividad de los existentes. ¿Se te dan bien los idiomas o simplemente quieres practicar más? Puedes ayudar a traducir o mejorar las traducciones de las aplicaciones o si te sientes valiente, traducir la documentación de alguna aplicación. ¿Eres una persona sociable? Puedes ayudar a otros usuarios en los foros a solucionar sus problemas o contar las ventajas de KDE a quien creas que le pueda interesar. ¿Te gusta ser minucioso? Crea entradas en bugs.kde.org para que los desarrolladores conozcan los problemas que los usuarios tienen o revisa bugs que alguien haya reportado para comprobar si siguen siendo válidos o si están duplicados.

La Comunidad KDE

Define KDE en 3 palabras:
 Hace años habría dicho “Un gran escritorio”, pero hoy en día, sin desmerecer al escritorio, lo definiría como: Una gran comunidad.
Siempre se dice que KDE es una Comunidad ¿Tú qué opinas?
Es cierto, en KDE hay muchas personas de todos los rincones del planeta, con distintas culturas, costumbres, pero que tienen algo en común y es la visión del futuro que queremos en la informática y el deseo de hacer un entorno de escritorio y aplicaciones útiles, amigables, rápidas … y lo mas importante, libres y liberadoras.

KDE somos nosotros.

Te gusta asistir a los eventos ¿por qué? Cuéntanos alguna anécdota.
Anécdotas tengo muchas, quizás por contar alguna, cuando se hizo la reunión anual de desarrolladores y usuarios de KDE del 2003 (todavía no se llamaban Akademy, sino que cada año tenia un nombre distinto dependiendo del lugar donde se hiciera, de hecho, en la de Málaga fue cuando decidimos mantener el nombre Akademy, pero me estoy dispersando 🙂 ). En el 2003 la reunión anual se llamó Kastle y se hacía en un pueblecito de la República Checa llamado Nové Hrady que tenía una población de 2500 personas y donde nos quedábamos a dormir en un antiguo monasterio. Como estaba bastante inaccesible, KDE fletó un autobus que recorrió Alemania de norte a sur recogiendo colaboradores de KDE en distintas ciudades y llevándonos de camino al evento. Al intentar cruzar la frontera, nos tuvieron un rato retenidos porque había entre nosotros un desarrollador de Brasil, que al no ser europeo, nos dijeron que no podía pasar. Afortunadamente al final nos dejaron paso. Más tarde, el conductor del autobús se perdió y paramos otro rato para mirar mapas, llamar por teléfono a gente que sabía cómo llegar e intentar averiguar dónde estábamos y cómo llegar al destino. Lo que se dice un viaje interesante :).

Kastle, el evento internacional KDE de 2003.

Preguntas rápidas:

¿KDE 4 o Plasma 5?
Plasma 5
Aplicación que más te gusta de KDE
Es difícil elegir una, pero si dejamos aparte el propio Plasma, posiblemente habría empate entre digikam y kdeconnect.
Aplicación que te gustaría tener nativa en KDE
La verdad es que no hecho muchas cosas en falta en KDE, por decir algo, quizás me gustaría ver una aplicación tipo Logic Pro, Cubase o similar en Linux, siendo usada de forma profesional.
Captura de pantalla de tu escritorio

Sencillo el escritorio de Antonio, con el fondo por defecto de openSUSE Leap 42.1

La persona


Ya sabemos que en realidad KDE es una Comunidad formada por personas que crea Software para personas, así que me gustaría conocer un poco más  los integrantes y saber de sus gustos personales:

Un libro:
Una película:
Un artista musical:
Tu canción favorita:
Elegir una canción es complicado, pero el álbum completo “Zoolook” de Jarré es muy bueno y también “Live at the Acropolis” de Yanni.
Cuando estoy solo me gusta comer:
 Cualquier cosa que me dejen mis alergias.
Pues aprovechando la coyuntura, os pongo el álbum preferido de Antonio, seguro que ha escrito mucho código mientras lo escuchaba o resonaba en su cabeza. Jean Michel también es uno de mis músicos favoritos.

Ahora tu minuto de oro, cuenta lo que quieras para los lectores de KDE Blog.
Pues ya que se me da la oportunidad, voy a aprovechar para hacer publicidad de KDE España, la asociación que tenemos en España de usuarios y desarrolladores de KDE que se dedica a velar por los intereses de nuestro entorno favorito. Me gustaría comentar que se nos puede encontrar en https://www.kde-espana.org/ y que quien quiera puede suscribirse a nuestra lista de correo o incluso hacerse socio de la asociación.
Foto de grupo reducido Akademy-es 2016

Foto de grupo de Akademy-es 2016 de Madrd.

También felicitar a todos por el aniversario de KDE y que dentro de otros 20 años sigamos desarrollando el escritorio que queremos.

Muchas gracias por tu tiempo, estoy seguro que los lectores del blog habrán disfrutado tanto de la entrevista como yo.

Gracias a ti por este blog tan importante para KDE y por el trabajo de recopilar todas las entrevistas.

October 24, 2016

Getting the correct dependencies and up to date version of required libraries has always been a challenge for Kdenlive users. So we are pleased to announce that we now provide binary packages for download. These packages contain the latest Kdenlive development version (git master), as well as current development versions of MLT, Frei0r, OpenCV. The GPU movit library is not included at this stage. There might be some performance hit due to the nature of the formats, but these packages will be most helpful to debug and test the alpha/beta versions so that we can provide better releases. It will also help to identify issues linked to missing dependencies or outdated libraries on your system.

So if you are ready, you can download Kdenlive’s first AppImage here:
Then, simply make the file executable and run it! In a terminal:

  • chmod a+x kdenlive-16.12-alpha1-x86_64.AppImage
  • ./kdenlive-16.12-alpha1-x86_64.AppImage

We also provide a Snap package available for testing on Ubuntu distros:

  • sudo snap install --edge --force-dangerous --devmode kdenlive-devel
  • kdenlive-devel

The snap package is in the edge channel and requires “devmode” because of current limitations in the snap format.

These packages will not touch your system’s libraries, and can easily be removed. Please leave your feedback in the comments or on our mailing list(registration required) / forums.

We will provide several updates to this packages before the Kdenlive 16.12 release so that you can follow the development / bug fixes.

hace menos de una semana que se anunciaron las charlas que forman parte de la nueva serie de ponencias que organiza la UNED de Vila-real con el objetivo de potenciar el Conocimiento Libre. De esta forma este miércoles ya tenemos prevista la primer charla “Software Libre, mucho más que Software” y hoy me complace anunciar el segundo evento: el Taller de instalación de GNU/Linux en las V Jornades Libres. Una excelente oportunidad de iniciarse de una forma guiada en el mundo GNU/Linux.

Taller de instalación de GNU/Linux en las V Jornades Libres

El primer taller de las V Jornadas se celebrará el 28 de octubre a las 17 horas, el protagonista será GNU/Linux a cargo de Ignacio Monforte infomático del Centro Asociado de la UNED de Vila-real y colaborador muy activo de las Jornadas.

Esta jornada tiene como objetivo es familiarizarse con la instalación de una distribución GNU/Linux en un ordenador personal, lo cual realizaremos  mediante máquinas virtuales o en los portátiles u ordenadores de sobremesa que la gente traiga al taller.

Aprovecho para comentar que ya tenemos enlace para la emisión en streaming de la charla del próximo miércoles “Software Libre, mucho más que Software”: https://www.intecca.uned.es/portalavip/directos.php?ID_Grabacion=52548&ID_Sala=164360

Taller de instalación de GNU/Linux en las V Jornades Libres

La información básica del taller es la siguiente:

Otras informaciones útiles respecto a las V Jornades Lliures son las siguientes:

Agradecemos a la UNED de Vila-real las facilidades para realizar las charlas y los talleres, así como a toda la gente involucrada en las jornadas su buena predisposición.

¡Os esperamos el viernes!

October 23, 2016

It is available at the usual place https://community.kde.org/Schedules/Applications/16.12_Release_Schedule

Dependency freeze is in 2.5 weeks and Feature Freeze in 3.5 weeks, so hurry up!

Mageia KDE Team just finished to push in Mageia cauldron :
– Plasma 5.8.2 ( the Plasma LTS version )
– KDE Applications 16.08.2
– KDE Frameworks 5.27.0

If you find packaging bugs don’t hesitate and come in Mageia Bugtracker

And if you want to join KDE Team and help you can mail us or find us on IRC ( freenode  : #mageia-kde ).

KDE turned twenty recently, which seems significant in a world that seems to change so fast. Yet somehow we stay relevant, and excited to continue to build a better future.

Lydia asked recently on the KDE-Community list what we were most proud of.

For the KDE community, I'm proud that we continue to grow and change, while remaining friendly, welcoming, and ever more diverse. Our software shows that. As we change and update, some things get left behind, only to re-appear in fresh new ways. And as people get new jobs, or build new families, sometimes they disappear for awhile as well. And yet we keep growing, attracting students, hobbyist programmers, writers, artists, translators, designers and community people, and sometimes we see former contributors re-appear too. See more about that in our 20 Years of KDE Timeline.

I'm proud that we develop whole new projects within the community. Recently Peruse, Atelier, Minuet, WikitoLearn, KDEConnect, Krita, Plasma Mobile and neon have all made the news. We welcome projects from outside as well, such as Gcompris, Kdenlive, and the new KDE Store. And our established projects continue to grow and extend. I've been delighted to hear about Calligra Author, for instance, which is for those who want to write and publish a book or article in pdf or epub. Gcompris has long been available for Windows and Mac, but now you can get it on your Android phone or tablet. Marble is on Android, and I hear that Kstars will be available soon.

I'm proud of how established projects continue to grow and attract new developers. The Plasma team, hand-in-hand with the Visual Design Group, continues to blow testers and users away with power, beauty and simplicity on the desktop. Marble, Kdevelop, Konsole, Kate, KDE-PIM, KDElibs (now Frameworks), KOffice (now Calligra), KDE-Edu, KDE-Games, Digikamkdevplatform, Okular, Konversation and Yakuake, just to mention a few, continue to grow as projects, stay relevant and often be offered on new platforms. Heck, KDE 1 runs on modern computer systems!

For myself, I'm proud of how the KDE community welcomed in a grandma, a non-coder, and how I'm valued as part of the KDE Student Programs team, and the Community Working Group, and as an author and editor. Season of KDE, Google Summer of Code, and now Google Code-in all work to integrate new people into the community, and give more experienced developers a way to share their knowledge as mentors. I'm proud of how the Amarok handbook we developed on the Userbase wiki has shown the way to other open user documentation. And thanks to the wonderful documentation and translation teams, the help is available to millions of people around the world, in multiple forms.

I'm proud to be part of the e.V., the group supporting the fantastic community that creates the software we offer freely to the world.

October 22, 2016

We’re still fixing bugs like madmen… And working on some cool new features as well, but that’s for a later release. In any case, here is the second Krita 3.1 beta! Yes, you’re reading that correctly. Originally, we had planned to use 3.0.2 as the version for this release, but there is so much news in it that it merits a bigger version bump. Plus, with the acceptance of Julian Thijssens’ Google Summer of Code work by the Qt Project, we’re reaching a really big milestone:

From the next release on, Krita will officially support OSX.



That means that the OpenGL canvas works fully and that we’re committed to fixing OSX-specific bugs, just like we’re fixing bugs on Windows and Linux. It means we’re confident that you can use Krita 3.1 on OSX and be productive, instead of experimenting. So, please test this beta, and help us find bugs and issues!

Of course, Krita 3.1 will have much more new stuff. A new brush engine that supports really big brushes, Jouni’s Google Summer of Code work on adding new features to animation, Wolthera’s Google Summer of Code work that adds color managed high-channel depth color selectors and soft proofing to Krita, a stop-based gradient editor, ffmpeg-based export to animated gif and video formats. And much more.

Note: the beta still contains the colorize mask/lazy brush plugin. We will probably remove that feature in the final release because the current algorithm is too slow to be usable, and we’re still looking for and experimenting with new algorithms. With the current beta you will get a preview of how the user interface will work, but keep in mind that the we know that it’s too slow to be usable and are working on fixing that

The second beta is also much more stable and usable than the first beta (, and we’d like to ask everyone to try to use this version in production and help us find bugs and issues!



There is also a snap image available in the Ubuntu App Store, in the beta channel.


Source code

October 21, 2016

This announcement is also available in Italian, Spanish and Taiwanese Mandarin.

The latest updates for KDE's Plasma, Applications and Frameworks series are now available to all Chakra users.

The Plasma 5.8.2 release provides additional bugfixes to the many new features and changes that were introduced in 5.8.0 aimed at enhancing users' experience:

Applications 16.08.2 include more than 30 recorded bugfixes and improvements to 'kdepim, ark, dolphin, kgpg, kolourpaint, okular, among others'.

Frameworks 5.27.0 include a new set of mimetype icons, in addition to the usual bugfixes and improvements.

Other notable package upgrades and changes:


  • plasma-workspace now provides by default the ksuperkey package functionality.
  • php 7.0.11. The 5.6 series is now provided as php56.
  • gconf has been introduced as a dependency of plasma-pa.
  • intel-ucode 20160714
  • laptop-mode-tools 1.70
  • openssl 1.0.2.j
  • rust 1.12.0
  • filesystem 2016.09
  • gnutls 3.4.15
  • lua 5.3.3
  • vim 8.0.0045

  • libreoffice 5.2.2
  • kexi 3.0.0, now ported to Frameworks 5. If you get a warning about files already existing on the filesystem, please follow our FAQ documentation.
  • mpv 0.21.0
  • wireshark 2.2.1
  • nmap 7.30

  • filezilla 3.22.1

  • steam
  • wine 1.9.21
  • q4wine 1.3.3

    It should be safe to answer yes to any replacement question by Pacman. If in doubt or if you face another issue in relation to this update, please ask or report it on the related forum section.

    Most of our mirrors take 12-24h to synchronize, after which it should be safe to upgrade. To be sure, please use the mirror status page to check that your mirror synchronized with our main server after this announcement.
  • Like many photographers, I have a handful of hand-made favorite presets (most of them are included in the Daily Curves Set) in my photographic toolbox. But there is one preset in particular I use more often than others. I named it Spektrum, as it’s inspired by images from the Spektrum Berlin photo book by Matthias Heiderich.

    Continue reading

    Last official stable release was done more than 3 years ago, it was based on Qt/KDE 4 tech, after that a few fixes got in what would be 0.4.0 but as I needed to change my priorities it was never released.

    Thanks to Lukáš Tinkl it was ported to KF5, on his port he increased the version number to 0.5.0, still without a proper release distros rely on a git checkout.

    Since I started writing Cutelyst I had put a break on other open source projects by mostly reviewing a few patches that comes in, Cutelyst allows me to create more stuff that I get paid to do, so I’m using my free time to pick paid projects now. A few months ago Cristiano Bergoglio asked me about a KF5 port, and getting a calibration tool not to depend on gnome-color-manager, and we made a deal to do these stuff.

    This new release got a few bugs fixed, pending patches merged and I did some code modernization to make some use of Qt5/C++11 features. Oh and yes it doesn’t crash on Wayland anymore but since on Wayland the color correction is a task for the compositor you won’t be able set an ICC profile for a monitor, only for other devices.

    For the next release, you will be able to calibrate your monitor without the need for the GNOME tools.

    Download: http://download.kde.org/stable/colord-kde/0.5.0/src/colord-kde-0.5.0.tar.xz.mirrorlist

    You might have noticed there's KDevelop for Windows out now...

    Which is already great in itself! But now it's also possible to install it via the super popular Windows package manager for Windows, Chocolatey.

    Here's all you need (in case you already have Chocolatey installed on your system):

    • Start a Command Prompt as Administrator user
    • Type in choco install kdevelop to install
    • Start KDevelop via the Windows start menu

    That's it!

    Here's what it does:

    C:\WINDOWS\system32>choco install kdevelop  
    Installing the following packages:  
    By installing you accept licenses for the packages.
    kdevelop v5.0.2 [Approved]  
    Downloading kdevelop 64 bit  
      from 'http://download.kde.org/stable/kdevelop/5.0.2/bin/windows/kdevelop-5.0.2-x64-setup.exe'
    Progress: 100% - Saving 90.45 MB of 90.49 MB (94839304/94887333)  
    Download of kdevelop-5.0.2-x64-setup.exe (90.49 MB) completed.  
    Hashes match.  
    Installing kdevelop...  
    kdevelop has been installed.  
    Added C:\ProgramData\chocolatey\bin\kdevelop.exe shim pointed to 'c:\program files\kdevelop\bin\kdevelop.exe'.  
     The install of kdevelop was successful.
      Software installed as 'EXE', install location is likely default.
    Chocolatey installed 1/1 packages. 0 packages failed.  
     See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
    Check out Pro / Business for more features! https://chocolatey.org/compare
    C:\WINDOWS\system32>where kdevelop  

    Happy hacking!

    Thanks a lot to Hannah von Reth for setting up the KDE Chocolatey category, including publishing the KDevelop package there!

    As always, we ask you to provide us with any kind of feedback on the Windows version! It's much appreciated.

    October 20, 2016

    Amongst the 20 year of KDE parties around the world one of the busiest was held in Beijing. Dot News interviewed the organiser Leslie Zhai about KDE in China.

    KDE China's 20th Anniversary Group Photo

    Leslie Zhai

    Where are you from and what do you do for a living?

    I am from Wuhan, a very beautiful city in China. And I am working as a Linux developer at iSOFT in Beijing.

    How did you first start to use KDE software?

    In 2002, as a computer science major university student, I went to a Legal Authoried software store in Wuhan, Guangputun, and bought Redhat7 including four install CDs, three src.rpm CDs and a very exquisite user manual for only RMB 50, because other software for Windows 98 was too expensive to a univerty student! It was my first time to use KDE 3. Yes I chose KDE as my default desktop enviroment, but I tried GNOME of course. ;-) Then I tried to migrate my university's course assignment developed in Turbo C to compile with GCC. I used Konsole and VIM to edit my source code, I tried Emacs but I did not know how to make coffee with it, so I switched to VIM ;-) and my teachers switched to use Redhat8 instead of Windows 98 when teaching operating system courses.

    What are your activities contributing to KDE?

    As a KDE developer I fix bugs, I push to repositories after code is reviewed by other KDE developers, and I am maintaining K3b right now. My sincere thanks go to David Faure; he helped me when I broke the dependency freeze of libkcddb regarding the Applications/16.08 release. I migrated all projects using KF5Cddb, and right now libkcddb is KF5 ready! Also thanks go to Thomas Schmitt, one of the libburnia authors, he taught me a lot about ISO 9660 & MMC patiently and carefully!

    Talks at the Party

    Looks like you had a successful 20th anniversary party. Who was there and what did you all do?

    Yes! We had more people than we expected. We estimated there were only about 20 KDE users, but that day 65 KDE plus GNOME and other desktop enviroments users came! iSOFT KDE helped us so much to make the anniversary party happen. My old friend Conner Mo (the co-founder of linuxfans.org and magiclinux.org) came from Shanghai specially. We took a group photo wearing KDE 20 years T-shirts. The opening was by Cjacker Huang, the deputation of iSOFT sponsored this party, who is also a KDE developer since 2003! Happy birthday for KDE 20 years celebrated by Xiangkai Li, manager of iSOFT. Opening was by Lei Zhang. The deputation of LinuxCN sponsored this party, also shared updates with us. "Timeline.kde.org and Chinese KDE developers" shared by myself. Yunhe Guo (KDE-China l10n zh_CN translator) and csslayer (Fcitx and KDE developer) recorded video for the celebration. "GNOME Desktop and Foundation say happy birthday to KDE" was shared by Tong Hui. A delicious KDE 20 years cake. GNOME Foundation member was cutting cake and laughing happily. Announced kde-china.org. Enjoy KDE 20 years cake. So I changed my raffle script MAX to 65 on site. Raffle prizes were CHEERY keyboards, iSOFTLinux V4.0 USB sticks, KDE 20years T-shirts and more.


    What is China KUG and what does it plan to do?

    kde-china.org is the China KDE User Group for contributing to KDE:

    • Fixing bugs and code review
    • Translating l10n zh_CN
    • Akadamy-China ;-)

    How popular is Free and Open Source software in China?

    Very popular! A lot of internet companies use Open Source software such as Linux kernel, GNU toolchain, Nginx, MySQL, Memcached, Squid, DNF, Apt, Python, Django, reviewboard, PHP, Drupal, phpBB, flyspary, jQuery, Node.js, etc. in China.

    How popular is KDE software in China?

    Very popular! a lot of ArchLinux and Fedora fans use KDE! iSOFTLinux, MagicLinux, Kubuntu, openSUSE and RedflagLinux distributions choose KDE as their default desktop enviroment in China.

    The article on linux.cn mentions iSOFT has its own operating system using KDE software, can you tell us how this is made and what it's used for?

    iSOFTLinux V4.0 x86-64 is Cjacker Core base, default desktop enviroment is KDE (GNOME optional), easy-to-use Linux Desktop for end-users.

    How good is KDE software's support for CJK writing systems?

    Thanks for Fcitx maintained and developed by csslayer, also his kimpanel work, it all works very good for KDE!

    Cutting the Cake

    Why do we not hear more from Chinese people on KDE mailing lists, forums and chat channels?

    First, language issues. For example I often wrote email in Chinglish just like my answers to this interview ;-) but KDE developers are very clever in understanding what I tried to express. Second, the timezone issue. I would update my patch in the morning, then wait for review, perhaps the next morning I could receive the reply. You can see the waiting time, so it is difficult to chat with each other in IRC. So we prefer to use reviewboard and Bugzilla to communicate with other KDE developers.

    Anything else you'd like to say?

    I hope more and more Chinese internet companies join the Open Source game, they are using a lot of open source utilities and libraries, but many core and important applicationa are not available for Linux desktop users. Even binary-only just like Skype is OK!

    Thanks for your answers!

    While Timothee Giet is working on the next Krita training video series — and it’ll all be about animation! — we’re cutting the price of our existing training videos!

    Digital downloads

    Muses, still one of the best introduction to digital painting in general, and to Krita in particular, is now available for only €14,95!

    Muses Download

    Now just €14,95, from €24,95

    And Secrets of Krita, full of in-depth hints, tricks and tips on how to get the most out of Krita is now also… only €14,95!

    Secrets of Krita – Download
    Now just €14,95, from €29,95

    You can also get these downloads from our gumroad shop!


    We still have actual DVD’s, neatly printed with atractive covers available for you to order, too:

    Secrets of Krita – DVD
    Now just €14,95, from €29,95, including shipping

    Muses DVD
    Now just €14,95, from €24,95, including shipping


    Or you can get both training dvd’s and the latest version of Krita for Windows, OSX and Linux on a cool credit-card sized USB stick, showing off spring Kiki.

    USB-stick up-to-date
    Now just €24,95, from €39,95, including shipping

    October 19, 2016

    FOSDEM is one of the largest (5,000+ hackers!) gatherings of Free Software contributors in the world and happens each February in Brussels (Belgium, Europe).

    Once again, one of the tracks will be the Desktops DevRoom (formerly known as “CrossDesktop DevRoom”), which will host Desktop-related talks.

    We are now inviting proposals for talks about Free/Libre/Open-source Software on the topics of Desktop development, Desktop applications and interoperability amongst Desktop Environments. This is a unique opportunity to show novel ideas and developments to a wide technical audience.

    Topics accepted include, but are not limited to:

    • Open Desktops: Gnome, KDE, Unity, Enlightenment, XFCE, Razor, MATE, Cinnamon, ReactOS, CDE etc
    • Closed desktops: Windows, Mac OS X, MorphOS, etc (when talking about a FLOSS topic)
    • Software development for the desktop
    • Development tools
    • Applications that enhance desktops
    • General desktop matters
    • Cross-platform software development
    • Web
    • Thin clients, desktop virtualiation, etc

    Talks can be very specific, such as the advantages/disadvantages of distributing a desktop application with snap vs flatpak, or as general as using HTML5 technologies to develop native applications.

    Topics that are of interest to the users and developers of all desktop environments are especially welcome. The FOSDEM 2016 schedule might give you some inspiration.


    Please include the following information when submitting a proposal:

    • Your name
    • The title of your talk (please be descriptive, as titles will be listed with around 400 from other projects)
    • Short abstract of one or two paragraphs
    • Short bio (with photo)
    • Requested time: from 15 to 45 minutes. Normal duration is 30 minutes. Longer duration requests must be properly justified. You may be assigned LESS time than you request.

    How to submit

    All submissions are made in the Pentabarf event planning tool: https://penta.fosdem.org/submission/FOSDEM17

    To submit your talk, click on “Create Event”, then make sure to select the “Desktops” devroom as the “Track”. Otherwise your talk will not be even considered for any devroom at all.

    If you already have a Pentabarf account from a previous year, even if your talk was not accepted, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have any issues with Pentabarf, please contact desktops-devroom@lists.fosdem.org.


    The deadline for submissions is December 5th 2016.

    FOSDEM will be held on the weekend of 4 & 5 February 2017 and the Desktops DevRoom will take place on Sunday, February 5th 2017.

    We will contact every submitter with a “yes” or “no” before December 11th 2016.

    Recording permission

    The talks in the Desktops DevRoom will be audio and video recorded, and possibly streamed live too.

    In the “Submission notes” field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example:

    “If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>.”

    If you want us to stop the recording in the Q & A part (should you have one), please tell us. We can do that but only for the Q & A part.

    More information

    The official communication channel for the Desktops DevRoom is its mailing list desktops-devroom@lists.fosdem.org.

    Use this page to manage your subscription: https://lists.fosdem.org/listinfo/desktops-devroom


    The Desktops DevRoom 2017 is managed by a team representing the most notable open desktops:

    • Pau Garcia i Quiles, KDE
    • Christophe Fergeau, Gnome
    • Michael Zanetti, Unity
    • Philippe Caseiro, Enlightenment
    • Jérome Leclanche, Razor

    If you want to join the team, please contact desktops-devroom@lists.fosdem.org

    The FreeBSD packages of KDE software — the KDE 4 desktop, and soon KDE Frameworks 5 and Plasma 5 Desktop and KDE Applications — have traditionally been shipped pretty much as delivered from the upstream source. We compile, we package, and there is very little customization we do as a “distro”. The KDE 4 packages came with a default wallpaper that was a smidgen different from the one shipped with several Linux distro’s. I think Ivan Cukic did that artwork originally. For Plasma 5 Desktop, we also wanted to do a tiny bit of branding — just the default wallpaper for new users, mind.

    Thanks to the tremendously helpful Plasma crew who answered my questions about setting a default wallpaper by producing the necessary files on the spot. After a tiny amount of massaging, I’ve now got a package that does the FreeBSD branding of the Plasma 5 Desktop for us. Of course we retain the upstream settings and wallpapers too.

    Also great thanks to Timothee Giet, for producing the image (based on his Flying Konqui) that we’re now going to use as the default wallpaper — Konqui flying on BSD, that’s just what we want, after all.

    Last weekend, I finished the construction part of my garden shed. The last bit mostly playing with the circular saw, taking rough boards and making them square, then angling them so that they would fit under the roof. It took a couple of hours, but I ended up filling the 3m-by-65cm gable with vertical planking, quite neatly. At the beginning of this year, I wouldn’t pick up a circular saw — power tools, scary. So I planned building a shed to force myself to learn something about carpentry. The next-door neighbour is a handyman, so we worked together and basically he taught me how to use the tools and get things done. (The Czech animation series “Pat a Mat” is popular in the Netherlands as “Buurman en Buurman“, and we style ourselves thus).

    Anyway, I think my point is that learning to use the tools is half the battle.

    So on the weekend I also worked on updating Qt 5.6.1 to Qt 5.6.2 on FreeBSD, which involves using new and scary tools as well. Power tools, they can be really useful, or they can take off a finger if you’re not careful. In this case it was Phabricator, which is also used in KDE — but not everywhere in KDE. For FreeBSD, the tool is used to review updates to ports (the packaging instructions), so I did an update of Qt from 5.6.1 to 5.6.2 and we handled the review through FreeBSD’s Phab. The ports infrastructure is stored in SVN, so the review is relatively straightforward: update the ports-tree checkout, apply your changes, use arc to create or update a review request. I was amazed by how painless it was — somehow I’d been frightened. Using the tool once, properly, makes a big difference in self-confidence.

    At this point, the tooling no longer stands in my way, and we can expect to have KDE-FreeBSD updates rolling out a little faster (until we’re caught up, finally). Current status is: Qt 5.6.2 is in exp-run (last stage before committing), KDE 4 infrastructure has landed, KF5 is being prepared for review by Tobias, and the plasma5/ branch of area51 contains the latest bits of everything released by the KDE community that we can port.

    Two weeks have passed since the Plasma 5.8 release and our Wayland efforts have seen quite some improvements. Some changes went into Plasma 5.8 as bug fixes, some changes are only available in master for the next release. With this blog post I want to highlight what we have improved since Plasma 5.8.

    Resize only borders

    KWin’s server side decorations have a feature that one can resize the window in the shadow area. With the Breeze window decoration this is available if one uses the border size “No Side Borders” or “No Borders”. For Wayland we just had to adjust the input area of a window slightly and honor it when evaluating the mouse pointer movements.

    Global Shortcut handling

    We found a few bugs related to global shortcut triggering. There is some unexpected behavior for shortcut triggering in xkbcommon, which will be addressed in the next release by adding new API. For now we had to workaround it to support some shortcuts which no longer triggered. Of course for every kind of shortcut which did not trigger we added a test case so we can also in future ensure that this works once the new xkbcommon release is available. At the moment we are not aware of any not working global shortcuts on Wayland. If you hit one, please report a bug.

    Support for Keyboard LEDs through libinput

    KWin did not enable the LEDs for num lock, caps lock, etc. This was mostly because I don’t have any keyboard which has such LEDs – neither my desktop keyboard nor my two notebooks have any LEDs. So I just didn’t notice that this was missing. Once we got the bug report we looked into adding this. I want to take this as an example of the “obvious bug” one doesn’t report because it’s so obvious. But if one doesn’t have such hardware it’s not so obvious any more.

    Relative pointer support

    A feature we added for Plasma 5.9 is support for the relative pointer protocol.

    Relative Pointer Events

    The protocol is implemented in KWayland 5.28 and KWin is adjusted to support the relative pointer events as can be seen in the screenshot of the input debug console. This is a rather important protocol to support games on Wayland. We also plan to add pointer confinement for Plasma 5.9.

    Move windows through the widget style

    Our widget styles Breeze and Oxygen have a feature to move the window when clicking in empty areas. This is a feature which needs to interact with the windowing system directly as Qt doesn’t provide an abstraction for it. On X11 it uses the NETRootInfo::moveResizeRequest, on Wayland support for triggering a window move is built into the core protocol. But so far we were not able to provide the feature on Wayland as we just didn’t have enough information from QtWayland. For example we lacked access to the wl_shell_surface on which we have to trigger the move. So some time ago I added support to QtWayland that we can access the wl_shell_surface through the native interface. Now about a year later we can start to use it. To support this feature we need to create an own wl_seat and wl_pointer object and track the serial of pointer button press. This we can then pass to the move request on the ShellSurface. The change is not KWin specific at all and will work on all Wayland compositors.

    Color scheme sync to decoration

    A new feature we added in KWin 5.0 is the possibility to synchronize the color scheme from the window into the window decoration and the context menu on the decoration. On X11 this works through a property which our KStyle library sets. This was the best we had back in the early days of the 5.x series as Qt didn’t expose enough information. It has the disadvantage that the sync only works with QWidget based applications and only with widget styles inheriting KStyle. For Plasma 5.9 we improved that and brought the relevant code into plasma-integration. The restriction to QWidget is gone and it works now with all kind of windows by listening to the QPlatformSurfaceEvent. This very useful event which got added in Qt 5.5. It informs us when a native window is created for a QWindow. Thus we can add our own X11 properties on the native window directly after creation and before the window is mapped.

    Custom color scheme support

    While adjusting this code for X11 we also added the relevant bits for Wayland. We use the Qt Surface Extension protocol to pass a property to the server. That’s a small and neat addition the Qt devs did to allow communication between a Qt based client and a Qt based Wayland compositor. As one can see in the screenshot the color scheme now updates also for Wayland applications.

    Window icons

    Window icon handling in Wayland is different to X11. On X11 the icons are passed as pixmaps. That has a few disadvantages nowadays because the icons provided on the window might not have a high enough resolution to work well on high-dpi systems. The icon from the icon-theme though provides higher resolution. On Wayland there is no way to pass window icons around and the compositor takes the icon from the desktop file of the application. This works well unless we don’t have a desktop file. For such windows we now started to use a generic Wayland icon as the fallback, just like we use a generic X icon as fallback for X11 windows which don’t have an icon.

    Proper icons for X windows in task manager

    That’s an icon which one might have noticed when using a Plasma Wayland session as every Xwayland window only had the generic X icon in the task manager. The communication between KWin and the task manager also passes the icon name around and not pixmap data. This works well for everything which isn’t Xwayland where we normally just don’t have the name. For Plasma 5.9 we addressed this problem and extended our protocol to request pixmap data for a window icon which doesn’t have a name. Thus we are now able to also support Xwayland windows, which increases the useability of the system quite a lot.

    Multi screen effect improvements

    On Wayland several of our effects broke in a multi-screen setup. This is because rendering is different. On X11 all screens are rendered together in one rendering pass and we have one OpenGL window to render to. On Wayland we have one OpenGL window per screen and have one rendering pass per screen. That’s something our effects didn’t handle well and resulted in rendering issues. For Plasma 5.9 these issues are finally resolved.

    Wobbly windows

    One of the affected effects is Wobbly windows. A rather important effect given that this blog is subtitled “From the land of wobbly windows”. We experienced that in a multi-screen setup the effect was only active on one screen. If the window got moved to the other screen it completely vanished.

    I was quite certain that this is not a problem with the effect itself, but rather with the way how we render. As we also saw other effects having rendering issues in multi-screen setups I was quite optimistic that fixing wobbly would fix many effects.

    The investigation showed that the problem in fact was an incorrect area passed to glScissor due to the general changes in rendering explained above. Rendering on other screens got clipped away. With the proper change we got wobbly working and several other effects (Present Windows, Desktop Grid, Alt+Tab for example) without having to touch the effects at all.


    With that knowledge in place we looked into fixing other effects. E.g. the screenshot effect which allows to save a screenshot in the tmp directory. A few example of screenshots taken with this effect can be seen in this blog post. The problem with this effect was that when taking a fullscreen shot over all screens only one got captured. The assumption here was that our glBlitFramebuffer code needs adjustment to be per output and with that we can now screenshot every screen individually or all screens combined.

    Multi-screen shot with blur

    Blur and Background Contrast

    Related to that are the blur and background contrast effect as they also interact with the frame buffer, though don’t use the glBlitFramebuffer extension. With those effects one of the biggest problems was that the viewport got restored to a wrong value after unbinding the frame buffer object. Due to that the rendering got screwed up and we had severe rendering issues with blur on multi screen. These issues are now fixed as can be seen in the screenshot above: both screens are rendered correctly even with blur enable.

    Panel improvements

    Plasma’s panel got some improvements for Plasma 5.9. This started from bug reports about windows can cover not working and also auto-hide not working. Another example that it is important to report bugs.

    Auto hiding panel

    On X11 auto hiding panels use a custom protocol with KWin to indicate that they want to be restored if the mouse cursor touches the screen edge. It uses low level X11 code thus we also need a low level Wayland protocol for it. We extended our plasma shell protocol to expose auto hiding state and implemented it in both KWin and Plasma.

    Search in widget explorer

    We had a bug report that search in the widget explorer doesn’t work. The investigation showed that the reason for that is that the widget explorer is a panel window and we designed panels on Wayland so that they don’t take any keyboard focus. This is correct for the normal panel, but not for this special panel. We adjusted our protocol to provide an additional hint that the panel takes focus and implemented this in kwayland-integration in a way that the widget explorer gains focus without any adjustments to it.

    KRunner as a panel

    Of course there are more potential users for this new feature. One being KRunner. Once we had the code in place we decided to make KRunner a Panel on Wayland which brings us quite some improvements like it will be above other windows and on all desktops.

    October 18, 2016

    One of the key points of Plasma is while giving a simple default desktop experience, not limiting the user to that single, pre-packed one size fits all UI.
    Its strength is to be flexible to greatly different user needs, “Simple by default, powerful when needed”.
    Several years ago, the Visual Design Group had the idea of making easy to build and share desktop layouts to make easy to test wildly different user interfaces, see this old post by Thomas on the topic.
    Since then, work on it has been going on, mostly on the infrastructure needed to make it a reality, and in Plasma 5.8 the first pieces are there, tough still far from the complete experience we want to offer.

    The support for Look and Feel packages is there since a while (5.3 or so) that’s what one of those package can do:

    • Provide a default layout for when Plasma starts for the first time, it was used for distributions to personalise their UI, but now is easier for users as well.
    • Provide some default look options, like what color scheme to use, what icon theme etc
    • (advanced) provide the actual implementation of some UI, such as KRunner, the Alt+Tab window switcher dialog, the lock screen

    So far the default Plasma layout provided by the Look and Feel theme was used only when starting up for the first time, on a clean user home (therefore very useful for distributions) but sice Plasma 5.8, in the Workspace theme -> Look & Feel section of system settings there is an option to load the new layout when switching the look and feel theme. Not as default as is a destructive action that will remove your current Desktop setup.


    The other component is a tiny little application shipped in the “Plasma Sdk” package that’s called lookandfeelexplorer.
    With this applciation you can:

    • Create a new Look and Feel theme
    • Edit the metadata and thumbnail of a locally created/installed theme
    • Create a default javascript desktop layout based upon your current Plasma setup
    • Create a defaults file based upon your current setup as well, such as color scheme and icon theme

    The last two are the central part of sharing your idea of “the perfect desktop” with others, linked with the integration between the Look & Feel systemsetting module and the KDE store, also new in Plasma 5.8.

    It’s still a preliminary feature, as ideally in the future if your shared Look & Feel theme depends for instance from a particular icon theme or a particular 3rd party plasmoid, the store integration will download those dependencies as well.

    My Plasma Desktop in 2016My Plasma Desktop in 2016
    On Monday, KDE’s Plasma team held its traditional kickoff meeting for the new development cycle. We took this opportunity to also look and plan ahead a bit further into the future. In what areas are we lacking, where do we want or need to improve? Where do we want to take Plasma in the next two years?

    Our general direction points towards professional use-cases. We want Plasma to be a solid tool, a reliable work-horse that gets out of the way, allowing to get the job done quickly and elegantly. We want it to be faster and of better quality than the competition.

    With these big words out there, let’s have a look at some specifics we talked about.

    Release schedule until 2018

    Our plan is to move from 4 to 3 yearly releases in 2017 and 2018, which we think strikes a nice balance between our pace of development, and stabilization periods around that. Our discussion of the release schedule resulted in the following plan:

    • Plasma 5.9: 31 January 2017
    • Plasma 5.10: May 2017
    • Plasma 5.11: September 2017
    • Plasma 5.12: December 2017
    • Plasma 5.13: April 2018
    • Plasma 5.14 LTS: August 2018

    A cautionary note, we can’t know if everything exactly plays out like this, as this schedule, to a degree depends on external factors, such as Qt’s release schedule. Here’s what we intend to do, it is really our “best guess”. Still, this aligns with Qt’s plans, who are also looking at an LTS release in summer 2018. So, what will these upcoming releases bring?

    Breeze Look and Feel
    Breeze Look and Feel

    UI and Theming

    The Breeze icon theme will see further completion work and refinements in its existing icons details. Icon usage over the whole UI will see more streamlining work as well. We also plan to tweak the Breeze-themed scrollbars a bit, so watch out for changes in that area. A Breeze-themed Firefox theme is planned, as well as more refinement in the widget themes for Qt, GTK, etc.. We do not plan any radical changes in the overall look and feel of our Breeze theme, but will further improve and evolve it, both in its light and dark flavors.

    Feature back-log

    The menu button is a first sign of the global menu returning to PlasmaThe menu button is a first sign of the global menu returning to Plasma
    One thing that many of our users are missing is support for a global menu similar to how MacOS displays application menus outside of the app’s window (for example at the top of the screen). We’re currently working on bringing this feature, which was well-supported in Plasma 4 back in Plasma 5, modernized and updated to current standards. This may land as soon as the upcoming 5.9 release, at least for X11.

    Better support for customizing the locale (the system which shows things like time, currencies, numbers in the way the user expects them) is on our radar as well. In this area, we lost some features due to the transition to Frameworks 5, or rather QLocale, away from kdelibs’ custom, but sometimes incompatible locale handling classes.


    The next releases overall will bring further improvements to our Wayland session. Currently, Plasma’s KWin brings an almost feature-complete Wayland display server, which already works for many use-cases. It hasn’t seen the real-world testing it needs, and it is lacking certain features that our users expect from their X11 session, or new features which we want to offer to support modern hardware better.
    We plan to improve multi-screen rendering on Wayland and the input stack in areas such as relative pointers, pointer confinement, touchpad gestures, wacom tablet support, clipboard management (for example, Klipper). X11 dependencies in KWin will be further reduced with the goal to make it possible to start up KWin entirely without hard X11 dependencies.
    One new feature which we want to offer in our Wayland session is support for scaling the contents of each output individually, which allows users to use multiple displays with vastly varying pixel densities more seamlessly.
    There are also improvements planned around virtual desktops under Wayland, as well as their relation to Plasma’s Activities features. Output configuration as of now is also not complete, and needs more work in the coming months. Some features we plan will also need changes in QtWayland, so there’s some upstream bug-fixing needed, as well.

    One thing we’d like to see to improve our users’ experience under Wayland is to have application developers test their apps under Wayland. It happens still a bit too often that an application ends up running into a code-path that makes assumptions that X11 is used as display server protocol. While we can run applications in backwards-compatible XWayland mode, applications can benefit from the better rendering quality under Wayland only when actually using the Wayland protocol. (This is mostly handled transparantly by Qt, but applications do their thing, so unless it’s tested, it will contain bugs.)


    Plasma’s Mobile flavor will be further stabilized, and its stack cleaned up, we are further reducing the stack’s footprint without losing important functionality. The recently-released Kirigami framework, which allows developers to create convergent applications that work on both mobile and desktop form-factors, will be adjusted to use the new, more light-weight QtQuick Controls 2. This makes Kirigami a more attractive technology to create powerful, yet lean applications that work across a number of mobile and desktop operating systems, such as Plasma Mobile, Android, iOS, and others.

    Plasma DiscoverDiscover, Plasma’s software center integrates online content from the KDE Store, its convergent user-interface is provided by the Kirigami framework

    Online Services

    Planned improvements in our integration of online services are dependency handling for assets installed from the store. This will allow us to support installation of meta-themes directly from the KDE Store. We want to also improve our support for online data storage, prioritizing Free services, but also offer support for proprietary services, such as the GDrive support we recently added to Plasma’s feature-set.

    Developer Recruitment

    We want to further increase our contributor base. We plan to work towards an easier on-boarding experience, through better documentation, mentoring and communication in general. KDE is recruiting, so if you are looking for a challenging and worthwhile way to work as part of a team, or on your individual project, join our ranks of developers, artists, sysadmins, translators, documentation writers, evangelists, media experts and free culture activists and let us help each other.

    I’ve always loved diving down while snorkeling or swimming, and it’s been intriguing to me how long I can hold my breath, how far and deep I could go just like that. (The answer so far, 14m.)

    Last week, I met with Jeanine Grasmeijer. Jeanine is one of the world’s top freedivers, two times world record holder, 11 times Dutch national record holder. She can hold her breath for longer than 7 minutes. Just last month she dove down to -92m without fins. (For the mathematically challenged, that’s 6.6 times 14m.)

    Diving with Jeanine GrasmeijerDiving with Jeanine Grasmeijer
    Jeanine showed me how to not breathe properly.
    We started with relaxation and breathing exercises on dry land. Deep relaxation, breathing using the proper and most effective technique, then holding  breath and recovering.
    In the water, this actually got a bit easier. Water has better pressure characteristics on the lungs, and the mammalian diving reflex helps shutting off the air ways, leading to a yet more efficient breath hold. A cycle starts with breathing in the water through the snorkel for a few minutes, focusing on a calm and regular, relaxed breathing rhythm. After a few cycles of static apnea (breath holding under water, no movement), I passed the three-minute-mark at 3:10.
    We then moved on to dynamic apnea (swimming a horizontal distance under water on one breath). Jeanine did a careful weight check with me, making sure my position would need as little as possible correction movements while swimming. With a reasonable trim achieved, I swam some 50m, though we mainly focused not on distance, but on technique of finning, arms usage and horizontal trim.
    The final exercise in the pool was about diving safety. We went over the procedure to surface an unconscious diver, and get her back to her senses.

    Freediving, as it turns out, is a way to put the world around on pause for a moment. You exist in the here and now, as if the past and future do not exist. The mind is in a completely calm state, while your body floats in a world of weightless balance. As much as diving is a physical activity, it can be a way to enter a state of Zen in the under water world.

    Jeanine has not only been a kind, patient and reassuring mentor to me, but opened the door to a world which has always fascinated and intrigued me. A huge, warm thanks for so much inspiration of this deep passion!

    Harbor porpoise MichaelThe cutest whale in the world!

    In other news on the “mammals that can hold their breath really well” topic: I’ve adopted a cute tiny orphaned whale!

    October 17, 2016

    Yay! My last event of 2016!

    I’m almost 600 kilometers of my town. On the Federal University of Lavras, Minas Gerais.

    I submitted a proposal to do a talk here. The organization accepted, and this afternoon I made a talk about Qt with the title: Qt – Your toolkit Python/C++ with the real write once, deploy everywhere.

    When I thought about this title, needs to be kind sensationalist, to call for people to come. Python calls people. And the doodle: Write once, deploy everywhere, to tease up the Java guys xD

    I did a talk for almost 100 people, and was very good!

    My first question was how many people in the room knew Qt, only 4 persons raised their hands… Well, now everyone in that class knows Qt because I think that I did a good job on the explanation hahahaha



    One of the surprises was that when I start to explain an example of how you can use CMake to handle differences between operational systems, I asked the crowd: – Ah, you guys use Windows? A heard a big no, so I asked how many people use Linux, 90% of the crowd raised their hands! Was a big difference from any other events that I asked that same question!

    I explained to them what is Qt, how the API’s is used, the difference between the open source and commercial licenses, what kind of apps exists, on the market that is written in Qt, I specific talked about KDE apps like Marble, Minuet, KDE Connect(That I used in my presentation) and Atelier. You can check my presentation on this link, however, is in Portuguese.

    The students made questions like:

    • If the support of Qt to mobile devices is very stable
    • Qt for embedded devices
    • Community
    • If Qt is easy to learn

    I think that all the talks that I did this year, this one was the most productive! I had a good base of Qt to explain with confidence what I want, I did good examples, and that I can thank Lamarque Souza that reviewed my presentation and gave to me good feedbacks.

    On the spare time, I started to play with my Arduino Mega and sensors again. I’ve played around with LEDs and the LCD monitor, where I was able to do it a good KDE birthday message:



    Playing with LEDs… =D

    You can find some videos of what I did with the Arduino on my Instagram account: lays147

    Also, I pushed all my sketches to my Github account, and you can check here.

    Now it prepares for the upcoming events in 2017, beginning with the 10º edition of Campus Party Brazil, in January, that have the promise to be a big party!

    That’s all folks!

    KDevelop 5.0.2 released for Windows and Linux

    Four weeks after the release of KDevelop 5.0.1, we are happy to announce the availability of KDevelop 5.0.2, a second stabilization release in the 5.0 series. We highly recommend to update to version 5.0.2 if you are currently using version 5.0.1 or 5.0.0.

    Along with the source code, we release an updated 64-bit AppImage for Linux as well as updated installers for Microsoft Windows. We've got the pleasure to announce a 32-bit version of KDevelop for Windows now, too!

    You can find all the downloads on our download page.

    KDevelop with two editors open in a split view

    Notable issues fixed in 5.0.2 are:

    • Fix a locking issue in the background parser, causing frequent crashes on Windows (3c395340d)
    • Fix broken search in the documentation view (0602281c)
    • Fix various issues with the breakpoints view (cba54572)
    • Fix a possible crash when activating a clang FixIt (BR: 369176)
    • Fix a crash when performing various actions with the Make plugin disabled (BR: 369326)
    • Fix text files being parsed as CMake under some circumstances, leading to bad performance and crashes
    • Use correct font in documentation view (BR: 285162)
    • Fix a crash when clicking "Rename declaration" without an editor being open (22bdccb1)
    • Fix "Download more ..." feature not working on some systems (4c4500bf)
    • Fix "Select next/previous toolview" behaving incorrectly in some cases (24d3e3bb)
    • Fix "Hide/Restore docks" behaving incorrectly in some cases (daeed5f1)
    • Fix "Install as root" action not working (30a66c3f)
    • Fix CMake build plugin sometimes rebuilding everything when it should not (17b6499e)
    • Various UI improvements.

    Fixes in the Windows installers:

    • Update Sonnet in the Windows installer which led to crashes when turning on Automatic Spell Checking [BR: 370470]
    • Fix heap corruption after start / immediately after opening folder [BR: 370495]

    The source code can be downloaded from http://download.kde.org/stable/kdevelop/5.0.2/src/.

    You can find the binaries for Windows and Linux on our download page.

    The source code archives and their sha-256 checksums are

    24ec89b4edc854808ce11a8e8b0aeb853f11926b26029bc46c80f901da00aec7  kdev-php-5.0.2.tar.xz
    5d160951933e2f6742a443e19d24e0c93a82567244500e4bb6a3124e5e4e11ff  kdev-python-5.0.2.tar.xz
    9b017901167723230dee8b565cdc7b0e61762415ffcc0a32708f04f7ab668666  kdevelop-5.0.2.tar.xz
    a7f311198bb72f5fee064d99055e8df39ecf4e9066fe5c0ff901ee8c24d960ec  kdevplatform-5.0.2.tar.xz

    For verifying integrity and authenticity of the files, the preferred method is to use the provided GPG signature files (.sig).
    All downloads are signed with the GPG key of Sven Brauch, fingerprint 329F D02C 5AA4 8FCC 77A4  BBF0 AC44 AC6D B297 79E6.

    sbrauch Mon, 10/17/2016 - 13:15


    Good show! I've updated the FreeBSD packaging of KDevelop 5.0 to this latest release (although it'll still be a while before that hits the official package servers). Thanks for creating KDevelop.

    Great, hope it can solve my problem of "Unable to resolve symbol of KDE_PLUGIN_VERSION" of 5.0.1.

    Btw, with 5.0.1 I can only have templates for KDE4, but no templates of KDE5, I think this may caused by the issue I mentioned above, will try the new one.

    I'm a bit confused about how the Windows version of 5.0 works. My understanding was that your using clang as the backend for all syntax highlighting and understanding of the code in version 5.0 of KDevelop. How does this work when on the Windows setup docs you say you can only use GCC (via MinGW) or Visual Studio? Does this mean that you are using Visual Studio for the Syntax highlighting and error messages, etc? Does that mean that your using the old parser that wasn't great? If this is the case is there any real reason to use KDevelop over other IDEs on Windows? Really hoping I am just missing something as KDevelop 5 on Linux is amazing and I would love to replace Visual Studio with it there as well.


    In reply to by James (not verified)

    Hey. For 5.0 we use the Clang backend on all platforms, that is Linux, OS X and Windows. All our C/C++ language support from 5.0 onwards is based on libclang (cf. http://clang.llvm.org/doxygen/group__CINDEX.html).

    We don't use VS nor do we use our "old parser". You can also use KDevelop with any compiler on Windows, be it MinGW, Visual Studio or even Clang on Windows; we don't actually care.

    What about just downloading the Windows version and giving it a spin? Would love to hear your feedback!


    In reply to by kfunk

    I also was confused by this. The instructions you link to on the download page say:
    "Note that we don't ship a C/C++ compiler. Instructions on how to set up a compiler and build system for C++ development can be found here."

    Those instructions linked there say that you need MinGW and Visual Studio and cmake.

    Regardless, I did try installing clang binaries and cmake. When I launch I get an error
    "Could not load project management plugin KDevCMakeManager."

    Also I am unable to compile or execute anything.


    In reply to by Jim (not verified)

    Yeah, please make sure cmake.exe is in system-wide PATH. We definitely need to communicate that better to the end user.

    Also, you need either MinGW orVisual Studio. Just one of these. Whatever the project you want to compile requires.

    Now I'm really confused. In you previous comment you stated:
    "For 5.0 we use the Clang backend on all platforms, that is Linux, OS X and Windows. All our C/C++ language support from 5.0 onwards is based on libclang (cf. http://clang.llvm.org/doxygen/group__CINDEX.html).

    We don't use VS nor do we use our "old parser". You can also use KDevelop with any compiler on Windows, be it MinGW, Visual Studio or even Clang on Windows; we don't actually care."

    But now you mentioned "Also, you need either MinGW or Visual Studio. Just one of these. Whatever the project you want to compile requires."

    Thanks for your replies but I'm really confused. Do you use clang or not on windows? If you have to use MinGW or the Visual Studio compiler why use Kdevelop 5.0 versus any other IDE on windows? What is parsing code on the windows version of KDevelop 5.0 Clang, MinGW or VS compiler?


    In reply to by Jim (not verified)

    For semantic highlighting of the C/C++ code we use libclang. On all platforms, even on Windows. The KDevelop installer we provide ships a libclang binary.

    For just browsing through code using KDevelop for Windows, you don't need anything, it's all there. Only if you intend to build your project on Windows, you need either MinGW, VC++.

    Hope that makes it clear now :)


    In reply to by Jim (not verified)

    There are two entirely separate things which many C++ IDEs historically mix, unfortunately.

    On the one hand, there's your toolchain, which you use to compile your code. What we _suggest_ to use is CMake as the build system and Microsoft's compiler, but anything else is possible as well -- KDevelop just invokes those tools as external programs and doesn't care much.

    On the other hand, and completely invisible to you normally, is the tooling the IDE uses internally to get information from your code. For this, we use libclang. This is for internal use by the IDE only though, it is not possible to use what we ship for compiling C++ code.

    We use clang everywhere. You still need your own compiler, be it clang, VS or gcc, to compile your code.

    Just tried out the linux AppImage on our Debian 7 (KDE 4.8) workplace platform. I wasn't able to run the image directly (missing fuse), but after renaming the image with an .iso extension, extracting the contents in ark, and launching AppRun, I am happy to see it running well! As we will be on Debian 7 for a little while longer, it's great to see that we will be able to run the latest KDevelop on an "old" system. Kudos!

    One item that wasn't working out of the box is spellcheck: Settings > Configure KDevelop > Editor > Editing > Spellcheck would display "No backend found for spell checking". After grabbing the debian sonnet-plugins package and extracting aspell.so, hspell.so, and hunspell.so to usr/lib/qt5/plugins/kf5/sonnet/ (in the tree extracted from the AppImage), spellchecking is back in business. Perhaps you can include these libs in future AppImage distributions.

    On kdevelop 4.7.2 we rely heavily on the kdevperforce and kdevcppcheck plugins. Any chance the kdevelop 5 libs for these plugins can be distributed as well, or made available in a separate package? Unfortunately I have no straightforward means of building them...


    In reply to by Martin (not verified)

    One item that wasn't working out of the box is spellcheck

    For this I've created https://phabricator.kde.org/T4100 -- you'll probably get that in another AppImage update.

    On kdevelop 4.7.2 we rely heavily on the kdevperforce and kdevcppcheck plugins

    kdev-perforce will be part of 5.1. You'll get that in the 5.1 AppImage.

    kdev-cppcheck unfortunately isn't released yet. We'd like to only ship released & tested modules in the AppImage. Let's see how far we get with cppcheck, maybe we can integrate it into KDevelop proper -- contributions welcome!

    Thanks Kevin, really appreciate your efforts! Great to hear about the upcoming kdev-perforce inclusion into the main branch. Maybe the kdev-cppcheck situation will give me the boost to look into the code at home. That said, I'm looking forward to seeing the semantic analyzer in action in the current 5.0.2 build.

    October 16, 2016


    Lakademy 2016 Group Photo.

    As many of you know, since 2012 we organize the Lakademy, a sort of Latin American Akademy. The event brings together KDE Latin American contributors in hacking sessions to work on their projects, promo meetings to think KDE dissemination strategies in the region and other activities.

    Every year we make a call for attendees. Anyone can participate, although the event is focused on Latin American contributors, we also want to encourage new people to become contributors and to join the community. So if you live in any country in Latin America and would like to join us at the next event, please complete this form showing your interest. This form will be available until the beginning of November.

    The next Lakademy will take place in the Brazilian city of Belo Horizonte, between April 28 and May 01. Remember that if you need help with the costs of travel and lodging, KDE e.V. can help you with this, but this will depend on several factors such as amount requested, number of participants in the event, how active you are in the community and so on. Do not be shy, we encourage you to apply and join our Latin American community. Maybe you are the next to host the Lakademy in your country. We would love to make an edition of the event in another country in Latin America other than Brazil.🙂

    See you at Lakademy 2017!

    Older blog entries

    Planet KDE is made from the blogs of KDE's contributors. The opinions it contains are those of the contributor. This site is powered by Rawdog and Rawdog RSS. Feed readers can read Planet KDE with RSS, FOAF or OPML.