Another month, another Plasma 6 update. I’ve been pretty busy during the past weeks, mostly further improving the Wayland session, fractional scaling, and dealing with Qt bugs. Working under the hood like this is tremendously important albeit somewhat ungrateful when there aren’t any pretty pictures to show.
A little over two months ago I involuntarily switched my daily driver laptop to a Plasma 6 development build (see this blog post on how that went). Since then there has been stunning progress on ironing out bugs, tidying things up, and implementing new features. Let me show you what I’ve been working on, stumbling blocks to look out for, and what you can do to help to make Plasma 6 a truly great release!
A couple of weeks ago I actually finally switched to a Plasma Wayland session full time and it’s been working great! This now also means I have to fix all of my pet peeve bugs, and boy did I!
Continue reading On the Road to Plasma 6, Cont’dI just returned from blazing hot Thessaloniki, Greece where the KDE Community’s annual conference Akademy was held this year. Unlike last year I stayed in the same hotel as many fellow KDE people so the pre-Covid Akademy vibes finally returned in the form of evening hotel lobby hacking. Sadly, I caught a gastrointestinal infection on Monday which made me fly home early and miss the day trip to Mount Olympus I had been looking forward so much.
After I accidentally screwed up my system Friday night, I ended up with no choice but to install all system updates from KDE neon “unstable” which now defaults to a Plasma 6 session. I certainly wasn’t planning on spending a few hours that evening fixing my setup. Alas, I am now taking “eating your own dog food” to the extreme and made my daily driver laptop run Plasma 6.
After what felt like an eternity we were finally able to come together in Augsburg, Germany for the Plasma Sprint that was originally planned for April of 2020, kindly hosted by TUXEDO Computers in their offices. There were sixteen attendees from six countries and it was great to have three newcomers on board, too.
Depending on your calendar system, another year is coming to a close very soon. While this year was a lot more enjoyable for many of us than the last two, we surely didn’t expect things to go downhill even more for others. As I am looking forward to some days off with my family, let me take a step back and reflect on some of the things I did in KDE in the last twelve months.
A while ago Google announced a new API level for browser extensions, named Manifest v3. You might have heard it in the news that it will impact the ability for extensions to arbitrarily filter traffic. While this particular aspect does not affect Plasma Browser Integration, there’s still a large number of behavior and API changes that we need to adapt to, especially when it comes to tampering with a website’s content. It’s getting more urgent as Chrome will stop stop running extensions still using the old version 2 by the end of this year!
Luckily, most extension features, namely KDE Connect integration, tabs and history runner, and download monitoring could be ported quite easily. However, media controls and Share API integration needed a significant rewrite in order to work with the new restrictions imposed on us, notably it is no longer possible for an extension to inject arbitrary inline JavaScript into websites. Many thanks to Fabian Vogt for refactoring this part of the extension!
A KIO worker for accessing iOS devices through the Apple File Conduit service.
While there have been several projects like this for both KDE 4 and Frameworks 5, this one has been written on top of the latest KIO classes and will be officially part of the next KDE Gear release. It is now part of the kio-extras module, which also houses the Android counterpart for transferring files over the MTP protocol.
Continue reading Introducing KIO AFCSometimes while using my computer I notice random slowness when launching a certain application or some feature that just doesn’t run very well. That’s always reason enough for me to take a deeper look.
My tool of choice for analyzing performance issues is Hotspot, KDAB’s excellent perf visualizer. It comes with an easy to use GUI for browsing the results collected by it. Particularly its flame graph lets you quickly detect, well, hotspots during execution. Just launch an application through Hotspot or attach it to a running one and look at the graphs. Depending on your system configuration you might need to adjust the perf_event_paranoid kernel setting in order for it to inspect other processes.
I just returned from this year’s KDE Akademy in Barcelona. After two years of only virtual sprints it has been great to finally meet up with many fellow KDE friends, most of which I haven’t seen since 2019, and also get to know some of the faces of people that have joined in-between.
