Planet KDE

Last week I attended the bi-annual OSM Hack Weekend in Karlsruhe again, hosted by Geofabrik, focusing on indoor routing as well as Transitous.

Structured Email / Semantic Web

But first to something different (skip to the next section for OSM content).

While traveling to Karlsruhe anyway I used the opportunity to meet with people working on Structured Email, something that has a lot of overlap with the travel document extractor used by KDE Itinerary.

There’s plenty of aspects for collaboration here:

• Sharing of test data. I learned about Web Data Commons for example, which is a giant corpus of structure data extracts from crawling the web by the University of Mannheim.
• Sharing of lessons learned, approaches and quirks/workarounds for processing structured data. We are currently lacking a forum for that.
• A standardized way for applications to register for handling a specific schema.org type. That way email clients or Plasma Browser Integration could dispatch objects they encounter to the respective application in a generic way, similar to how this is done for files based on MIME types. Ideally this is done on the XDG level, and while at it it’s probably worth looking at other areas where the same need came up (URLs, ActivityPub, barcode content, etc).

What we do in Itinerary for importing events, restaurants or hotels from websites is meanwhile also found in the Nextcloud Cookbook app, using the schema.org recipe data embedded in websites. And that’s still just scratching the surface, combining this with e.g. Open Food Facts could open very interesting possibilities. Very cool to see things like this being done :)

Indoor Routing

A month ago I had shown indoor routing running integrated in KDE’s indoor map demo application. That’s an important milestone, only the final 80% of the work remain now, namely making sure this produces reliable and useful results in a variety of locations.

Prefer corridors over rooms

Giving a computer the task of finding the shortest path will usually not yield practical results. That’s because human expectations around this contain many implicit assumptions, constraints and nuanced cost considerations that we all have to implement as well.

One example is shown below. The shortest path here crosses through two conference rooms or lecture halls, however you most likely don’t want to disturb whatever is ongoing in those rooms but rather take the slightly longer corridor around.

Shortest path (left), preferring corridors (right).

Giving different room types different routing cost factors helps with this.

Along the same line other details have been fixed or improved, such as:

• Emergency exists are not the same as regular doors.
• Not all OSM barrier types are actually blocking your way (eg. bollards, but also gates/turnstiles).

Data level of detail

Another aspect to deal with is that the OSM data in some places doesn’t have the necessary level of detail needed for routing. Examples include:

• Missing “cut outs” in the ground for stairs coming up from the floor below.
• Missing doors to rooms, staircases or elevator cabins.

Either of those can result in significant detours or even entirely inaccessible areas.

While augmenting the OSM data is the proper solution eventually, that is quite a large task. Fortunately we have a few workarounds and heuristics to deal with some of these issues:

• Stairs are now implemented as “off-mesh links” everywhere, rather than as 3D geometry as done previously, which allows “teleporting” through any obstacle on the way.
• We now drop walls around any elevator or staircase if there are no door nodes at all. That may lead to routing into those areas from the wrong side, but that’s still better than not being able access those at all.

With these improvements we can now also find a way out of the most complex test labyrinth so far, the Paris Metro.

Paris Metro station at Gare de l'Est. Data modelling

This work also identified a few issues where the OSM indoor data model is ambiguous or cannot express relevant details yet:

• There’s a significant difference between implicit walls on indoor=corridor elements in the Simple Indoor Tagging (SIT) scheme and usage in reality. No matter how you interpret that for routing you either end up either with unreachable areas or routes through walls.
• Similarly, there’s ambiguities on how (implicit) outer building walls should be mapped/interpreted.
• There is no way to model service counters that you might find at ticket offices or fast food stands. This matters to route towards the right side of a building/room.

See also the corresponding mailing list post for details, as well as the the upcoming quarterly OSM Indoor Meetup (Wednesday March 6th, 18:00 CET, online).

Transitous

Transitous, an effort to set up a free and open public transport routing service, also involves a lot of OSM data and software, so that was the other big topic for me.

Intermodal routing

While the public transport routing part for this works quite well already, enabling the intermodal routing has proven challenging. That is routing the first and last mile to and from public transport stops by foot/bike/scooter/car or a combination thereof, possibly considering things like available parking spaces or rental vehicles.

That is build on top of existing OSM routing engines, and MOTIS supports different options there as well. We haven’t found a combination yet that can import planet-wide data or at least data for all of Europe on the hardware we have (ie. needing significantly less than half a TB or RAM), offers the feature set needed by MOTIS for intermodal routing (1:1, 1:N and N:M routing, customizable profiles) and deliver all that with sufficient runtime performance. Bonus points for at least having the option for other advanced routing features (elevation support, realtime traffic support, etc).

There was a clear recommendation from the people running and developing those things professionally for GraphHopper. MOTIS has no support for that one yet, but it seems doable to add that. The bigger problem here is potentially that GraphHopper’s “Matrix API” (the part doing very efficient N:M routing) is apparently not available in the open source release. So we still don’t have a proper solution for this.

Geocoding

Another component needed for all this is address and POI search and as-you-type completion. There was an equally clear recommendation for Photon. That comes in an easy to get started package with a single binary and a pre-built database for a single country or the entire planet, but also allows to transition to a more complex setup enabling incremental data updates and offering a ton of options to fine-tune and customize the results (support more languages, bias towards certain types of locations, etc).

MOTIS integration for this also yet has to be done, but should be quite straightforward. Without intermodal routing this doesn’t gain us much on its own though.

Public transport coverage

Meanwhile the public transport coverage on Transitous is growing rapidly, see Jonah’s blog post on how to get your region included.

Transitous coverage in Europe.

If you are interested in collaborating on this, join the #opentransport Matrix channel and the Transitous Github project.

The mega-release has been such a mega amount of work that I’m a bit behind on my blogging, but don’t worry, the normal TWiK post will be out around this time tomorrow! Thanks for your patience, everyone.

KDE got accepted as a mentoring organization for Google Summer of Code 2024! Are you thinking about getting involved into KDE development? Check out the cool ideas KDE devs came up, they showcase what can be achieved by taking part as a student in GSoC. How to start? How to get involved? How to make an impression that will help your application?

Prerequisites

• You like KDE, you like us as a community, you can follow our philosophy, you like our product (a desktop or at least an specific application), and you resonate with our tech stack (C++, Qt, CMake).
• Grab some code from our GitLab, clone a repository and build it locally. This sounds easy. For first-timers it is not easy. Reach out for help in case you struggle.
• Run your self-built software. Now you can explore the joy of developing KDE.

You do not need an idea, at least not yet. Give it some time.

Get involved

Try getting involved. Usually it is not easy to fix bugs of implement a feature request from KDE bugtracking system. Some are hard to fix. Others need debates of future directions or best ways to get things done.

I propose you start looking for other opportunities:

1. Fix compiler warnings. Compilers analyze the code and as a result they might warn you. This can have various reasons like bad coding practice, code that is difficult to read and might easily be misread by humans, code with bad performance, bug-prone constructs.
   
2. Fix deprecation warnings. KDE, Qt, and every software evolves. Old interfaces are replaced by newer ones. The old ones are not directly thrown away, but deprecated. The deprecation warning reminds the developer to migrate from the old to the new interface. Some deprecations are trivial to fix, others require ample code changes.
   
3. Fix findings of static analyzers and linters. These are tools that analyze code more thorough compared to a compiler for the price of a longer runtime. They offer great hints for but are prone to false-positives (wrong warnings). Good tools for KDE are Cppcheck, Clazy and qmllint.
   
4. Fix crash bugs. Crashes often occur when the code contains memory issues. Examples are using objects that were deleted, accessing arrays out of bounds, de-referencing null pointers. Tools like a good debugger, Valgrind, and AddressSanitizer (and its cousins MemorySanitizer and UndefinedBehaviorSanitizer) help to localize the problem. Crashes are more difficult to understand and fix compared to warnings for tools.
   

Try to work for fixes of one to ten cases. More makes reviewing harder. Create a pull request and wait for feedback.

Rationale

Why do I think these areas are good to start working? The maintainer might reject your pull request. This can always happen. Compared to implementing a whole new feature, the amount of work you invested is limited.

Once you have an idea for GSoC and write your application, you can point to your pull requests as proof of work. Maintainers see your involvement, they see how you interact, and you get an early sense whether you like the contributing experience or not.

Even in the case that you do not want to become an GSoC student, you improved KDE a tiny little bit. Great feeling, isn't it?

Word of warning

Not everybody deem warnings worth to be fixed -- in general or in specific cases. You will learn what kind of warnings getting fixed are welcome. I already wrote a blog post about my experiences with fixing some Cppcheck in Kile.

First I would like to give a big congratulations to KDE for a superb KDE 6 mega release While we couldn’t go with 6 on our upcoming LTS release, I do recommend KDE neon if you want to give it a try! I want to say it again, I firmly stand by the Kubuntu Council in the decision to stay with the rock solid Plasma 5 for the 24.04 LTS release. The timing was just to close to feature freeze and the last time we went with the shiny new stuff on an LTS release, it was a nightmare ( KDE 4 anyone? ). So without further ado, my weekly wrap-up.

Kubuntu:

Continuing efforts from last week Kubuntu: Week 3 wrap up, Contest! KDE snaps, Debian uploads. , it has been another wild and crazy week getting everything in before feature freeze yesterday. We will still be uploading the upcoming Plasma 5.27.11 as it is a bug fix release and right now it is all about the finding and fixing bugs! Aside from many uploads my accomplishments this week are:

• Kept a close eye on Excuses and fixed tests as needed. Seems riscv64 tests were turned off by default which broke several of our builds.
• I did a complete revamp of our seed / kubuntu-desktop meta package! I have ensured we are following KDE packaging recommendations. Unfortunately, we cannot ship maliit-keyboard as we get hit by LP 2039721 which makes for an unpleasant experience.
• I did some more work on our custom plasma-welcome which now just needs some branding, which leads to a friendly reminder the contest is still open! https://kubuntu.org/news/kubuntu-graphic-design-contest/
• Bug triage! Oh so many bugs! From back when I worked on Kubuntu 10 years ago and plasma5 was new.. I am triaging and reducing this list to more recent bugs ( which is a much smaller list ). This reaffirms our decision to go with a rock solid stable Plasma5 for this LTS release.
• I spent some time debugging kio-gdrive which no longer works ( It works in Jammy ) so I am tracking down what is broken. I thought it was 2FA but my non 2FA doesn’t work either, it just repeatedly throws up the google auth dialog. So this is still a WIP. It was suggested to me to disable online accounts all together, but I would prefer to give users the full experience.
• Fixed our ISO builds. We are still not quite ready for testers as we have some Calamares fixes in the pipeline. Be on the lookout for a call for testers soon
• Wrote a script to update our ( Kubuntu ) packageset to cover all the new packages accumulated over the years and remove packages that are defunct / removed.

What comes next? Testing, testing, testing! Bug fixes and of course our re-branding. My focus is on bug triage right now. I am also working on new projects in launchpad to easily track our bugs as right now they are all over the place and hard to track down.

Snaps:

I have started the MRs to fix our latest 23.08.5 snaps, I hope to get these finished in the next week or so. I have also been speaking to a prospective student with some GSOC ideas that I really like and will mentor, hopefully we are not too late.

Happy with my work? My continued employment depends on you! Please consider a donation http://kubuntu.org/donate

Thank you!

Let’s go for my web review for the week 2024-09.

The KDE desktop gets an overhaul with Plasma 6

Tags: tech, kde, foss

A nice little review of our latest major releases. Looks like it’s well accepted so far. Very glad!

https://lwn.net/SubscriberLink/963851/0c64b8038c62432c/

Why I use Firefox

Tags: tech, mozilla, browser, privacy

All good reasons to use Firefox! I’m always about the market share of engines where we need diversity, but more good points are brought up here. It’s the only going the extra mile to respect your privacy while bringing innovative features too (tested the in browser translation recently and it’s great).

https://xn–ime-zza.eu/3

HDMI Forum Rejects Open-Source HDMI 2.1 Driver Support Sought By AMD - Phoronix

Tags: tech, hdmi, transparency, criticism, foss

The HDMI Forum is really an annoying body to say the least… they lack so much transparency.

https://www.phoronix.com/news/HDMI-2.1-OSS-Rejected

How Google helped destroy adoption of RSS feeds - Open RSS

Tags: tech, rss, google, criticism

I’m not sure if it’s malice… but for sure they harmed RSS use a lot during the years.

https://openrss.org/blog/how-google-helped-destroy-adoption-of-rss-feeds

Home Screen Advantage - Infrequently Noted

Tags: tech, apple, web, criticism

A bit of a long rant, still the core of the argument stays true. Apple will do everything in its power to keep their platform captive of their app store.

https://infrequently.org/2024/02/home-screen-advantage/

Bridging to Bluesky: The open social web, consent, and GDPR — UlrikeHahn

Tags: tech, fediverse, social-media, law, ethics

A good exploration of the Fediverse to Bluesky bridging debate from the angle of consent and the GDPR. It’s complicated and that shouldn’t come as unexpected.

https://write.as/ulrikehahn/bridging-to-bluesky-the-open-social-web-consent-and-gdpr

StreetPass for Mastodon

Tags: tech, fediverse, browser, web

Neat extension to blend your web browsing and discovering people on the Fediverse.

https://streetpass.social/

Hallucination is Inevitable: An Innate Limitation of Large Language Models

Tags: tech, ai, machine-learning, gpt

Interesting paper attempting to prove that hallucinations are unavoidable in those models. It is well balanced though, and explains why it’s not necessarily a bad thing in theory. In my opinion, the problem is the marketing talk around those models making grand claims or denying the phenomenon.

https://arxiv.org/abs/2401.11817

The Era of 1-bit LLMs: All Large Language Models are in 1.58 Bits

Tags: tech, ai, machine-learning, gpt

Might be an interesting trick to reduce the computation and energy costs of large language models. Let’s see if it gets replicated and generalized, this is a single short paper not peer reviewed anywhere as far as I can tell.

https://arxiv.org/abs/2402.17764

Git Tips 3: Really Large Repositories

Tags: tech, version-control, git, tools

Nice list of tips and recent git features to manage large repositories.

https://blog.gitbutler.com/git-tips-3-really-large-repositories/

Up to 10x faster strings for C, C++, Python, Rust, and Swift, leveraging SWAR and SIMD

Tags: tech, c++, python, performance

Interesting library if you got to do a lots of heavy analysis work with strings.

https://github.com/ashvardanian/StringZilla

Unreasonably effective - How video games use LUTs and how you can too

Tags: tech, graphics, 3d, video

Ever wondered how look-up tables are used for graphics? This is a good summary. Shows quite a few use cases which can come in handy.

https://blog.frost.kiwi/WebGL-LUTS-made-simple/

Look, Ma, No Matrices!

Tags: tech, mathematics, 3d, matrix

Interesting exploration of what could be done in a 3D engine using plane-based geometric algebra (PGA). This brings in nice properties that matrices don’t have. And the performance impact is apparently not as bad as one could have suspected. I definitely look more into it.

https://enkimute.github.io/LookMaNoMatrices/

MDN Curriculum

Tags: tech, mozilla, frontend, web, learning

Looks like a nice way to properly learn the web frontend basics.

https://developer.mozilla.org/en-US/curriculum/

Write Dumb Code — Matthew Rocklin

Tags: tech, programming, craftsmanship, complexity

Definitely this, mind the complexity you introduce in your code. Looking smart is not the goal here…

https://matthewrocklin.com/write-dumb-code.html

ARCHITECTURE.md

Tags: tech, foss, architecture

Good advice yes. Having a rough architecture document in a repository is more than welcome, it’s needed to help on-boarding. This is unfortunately not the norm in FOSS projects.

https://matklad.github.io/2021/02/06/ARCHITECTURE.md.html

Jevons Paradox doesn’t always apply to software

Tags: tech, software, performance, power

Interesting take even though I’m not sure I buy it completely. This is an interesting pledge for aiming at power efficiency and squeezing performance out of software.

https://pythonspeed.com/articles/software-jevons-paradox/

How Big Tech Runs Tech Projects and the Curious Absence of Scrum - The Pragmatic Engineer

Tags: tech, management, project-management, transparency, autonomy, craftsmanship, agile

To take with a pinch of salt since it has a couple of biases (most notably it focuses a lot on satisfaction) and the sample size is a bit small. A few interesting insights nonetheless. In particular it hints at autonomy, transparency, technical skills and vision as being the most important factors for satisfaction and success within teams. The applied project management method? Not so important it seems if the other factors are satisfied.

https://blog.pragmaticengineer.com/project-management-at-big-tech/

Agile software promises efficiency. It requires a cultural shift to get right

Tags: tech, agile, trust

Good summary of all the “fake agile” practice one can see. Without enough trust it’s not possible to put in place an agile organization.

https://www.runtime.news/agile-software-promises-efficiency-it-requires-a-cultural-shift-to-get-right/

Airfoil – Bartosz Ciechanowski

Tags: science, physics

Ever wondered how planes fly? What the Navier-Stokes equations lead to in practice? This is the right article.

https://ciechanow.ski/airfoil/

Bye for now!

Last night SUSE invited to their new Nürnberg offices at the Franken Campus in the city’s south for a KDE MegaRelease 6 release party. There were around 25 people from KDE, SUSE, and owncloud, with a good portion of non-contributors meeting some of the people behind their favorite desktop environment and suite of applications in-person for the first time.

Live demo of the latest and greatest KDE 1.1 on a ThinkPad 600E

After we had settled in, Dirk Müller gave an introductory speech about SUSE, followed by Cornelius Schumacher’s presentation about the history of KDE. Corneliuis showed pictures from how it all started and important milestones along the way. Some of them, like the infamous “KDE One” group photo, I already knew but also many I haven’t seen before. He also showed a couple of graphs illustrating the “KDE 4 Death Valley”, the two-and-a-half year gap between KDE 3.5 and 4.0, a very ambitious release, to put it mildly.

We surely learned our lesson from that and it’s also why for a transition between major releases, like from Plasma 4 to 5 ten (!) years ago, or now to Plasma 6, we set ourselves the goal of only freezing feature releases for a maximum of one year. Otherwise we’ll again lose many contributors, particularly new ones, that won’t see their hard work released for a very long time. Cornelius also counted a total of 530 stable KDE software releases since 1.0. We totally should have done 70 more for Plasma 6, right?

Afterwards I did a presentation on Plasma 6.0 (Slides, German, CC-BY-SA 4.0), an extended version of the interview I gave heise earlier this week, on what our goals were for the release, what’s actually changed, and a bit about the Wayland session which is now the default. Particularly the “older” folks in the room had to giggle when I mentioned the glorious Compiz days while talking about the return of the Desktop cube. Nicolas Fella then finished off by giving a presentation on KDE Frameworks 6 using an “eco-certified presentation software” with a “recycled slide deck” from his Akademy talk of 2021 – a good opportunity to reflect on which of the points we planned were actually implemented.

How to keep hackers happy: pizza, beer, and stickers

Just as we finished the presentations, pizza kindly sponsored by owncloud arrived and we rounded off the evening by chatting, eating pizza, and drinking beer. We also got a chance to toy around with KDE 1.1 on an old Thinkpad someone must have found in the archives. Sadly, we had to leave before 22:00 or else building security would have kicked us out. It seems, they have regular working hours at SUSE these days ;-) Thanks to everyone for organizing this party and I hope to see you all soon, not later than Akademy, our annual community conference, which is conveniently located in nearby Würzburg this year!

Plasma Mobile joins the Plasma 6 megarelease with a new shell and apps

The Plasma Mobile team is happy to announce the release of Plasma 6 for mobile devices!

It has been a long year of development and porting since our last major release of the shell, as well as mobile applications. This post will outline many of the highlights!

Housekeeping

The website was refreshed in anticipation for this release. Notably, the installation page was enhanced to better outline information about the various distributions that provide Plasma Mobile.

During the Plasma 6 development period, postmarketOS graciously provided us with a "nightly" repository of KDE packages tracking git repositories. We have found this critically useful for development. You can find instructions on how to use this repository here.

Plasma

Devin wrote a blog post covering some technical details covering the big aspect of the work porting all of the shell components to Qt and Plasma 6 APIs. A lot of functional work was done as well.

Homescreen

With Plasma 6, we are once again switching back to the Folio homescreen as default. The homescreen will once again have customizable pages to place apps and widgets, as well as an app drawer and search. Devin spent time rewriting it from scratch, addressing the limitations that existed in Plasma 5, in particular the customizations are now tied to each page, no longer causing reordering issues from screen rotations.

Notable Features:

• Customizable pages to place apps and widgets
• Folders
• Drag and drop customization
• Widgets (still some known issues, see below)
• App drawer (swipe up)
• KRunner search (swipe down)
• Row-column flipping for screen rotations
• Customizable row and column counts
• Customizable page transitions
• Import and exporting of homescreen layouts as files
• and more!

Interoperability

In Plasma 5, Plasma Mobile required several config files to be installed on the system in order to set some settings needed in Plasma. For Plasma 6, Devin created a new settings service that automatically handles this situation. This allows for interoperability with Plasma Desktop being simultaneously installed on the system, and eliminates the need to install custom configuration.

First time setup

Devin added an initial setup window that guides users to configure some basic aspects of the system, such as Wi-Fi and cellular settings.

Authentication dialog

Devin worked on porting the authentication dialog so that it has a mobile form factor.

Docked mode

Devin worked on adding a "docked mode" quicksetting which, when activated, enables window decorations and minimize/maximize/close buttons, and also stops enforcing application windows to be in fullscreen.

Navigation panel

Devin added a setting to always show the keyboard toggle button. He also made it so that if there is enough screen space, the panel goes on the bottom for tablets rather than on the side.

Task switcher

The task switcher was moved from the Plasma shell and into KWin to improve code maintainability.

Vibrations

In Plasma 5, the default vibration speed was hardcoded to the PinePhone's motor, which could not register lower vibration durations. This resulted in other devices having overly strong vibration effects. Vibrations now default to an acceptable level for other devices, and can still be configured in the shell settings module.

Flashlight

The flashlight quicksetting in Plasma 5 is hardcoded to the PinePhone. Florian worked on making it so that it now works with all phones in Plasma 6!

Settings

Devin improved the cellular settings module so that interaction tasks are asynchronous and do not freeze the UI. He also fixed unnecessary password prompts from being shown when the module is first opened.

Devin ported the Wi-Fi settings module to mobile form components, making it consistent with other modules. He overhauled the time settings module to newer components as well, making setting the time and date more intuitive. He also did some work to ensure the UI does not freeze when applying settings.

Joshua refactored the look and feel of the Push Notifications KCM and added UnifiedPush support to NeoChat so you'll never miss a message, even when NeoChat is closed (that is, if you want to get notifications, of course!)

Mathis created a new icon for the application.

Known Issues

Regrettably, our team resources are limited, and so we still have several outstanding issues that were not addressed in time for this release:

• Scrolling in Qt6 with a touchscreen has very low inertia compared to Qt5 and we cannot change the platform default, see this, reported in upstream to Qt here
• Some homescreen widgets open popups every time they are moved around
• Limited widget selection. Currently we just have existing widgets from the Plasma Desktop
• The screen recording quicksetting was removed for the time being. It needs further investigation on porting it to new APIs
• Gesture-only mode was removed for the time being. We need to investigate making KWin's gesture infrastructure fit our needs
• Sometimes application windows extend under the navigation bar. We need to investigate this regression with KWin
• The task switcher is slow on the PinePhone in particular. We need to investigate the performance of the KWin effect

There are other issues also being tracked in our issue tracker.

Applications

A tremendous amount of work went into the massive effort behind porting all of our applications to Qt6 and KF6. We would like to extend a big thank you to everyone involved!

Many major announcements for applications are in the Megarelease post, so be sure to check there too!

Photos (Koko)

While the application is still called Koko, user-facing text now calls it "Photos" to make it easier for you to find. (Devin Lin, KDE Gear 24.02, Link)

A new icon was created for the application, replacing the gorilla (Mathis Brüchert & Devin Lin, KDE Gear 24.02, Link)

Clock

The Clock app now pauses MPRIS media sources when an alarm or timer starts ringing and resumes (previously paused) sources once the alarm is dismissed (Luis Büchi, KDE Gear 24.02, Link)

Calculator

A new configuration page was added to the calculator app, allowing to set decimal places, angle units and a parsing mode (Michael Lang, KDE Gear 24.02, Link)

We improved the history view to allow for the removal of entries, and the drawer-style area for extra functions got replaced with a swipe view (Michael Lang, KDE Gear 24.02, Link 1, Link 2)

A number of new features and QoL improvements were added, including automatic font resizing when entering long expressions, better rendering of exponents, and more actual calculation features: random number, base n root/log, differential functions, standard deviations, and a lot more... Oh! and we switched math the engine to libqalculate! (Michael Lang, KDE Gear 24.02, Link 1, Link 2, Link 3, Link 4)

Kasts

Apart from some minor visual changes related to the Qt6 and KF6 update and several fixes regarding images and playback controls, Kasts will now update podcasts dramatically faster by not parsing RSS feeds that haven't changed (Bart De Vries, KDE Gear 24.02 Link 1)

The color theme (e.g. Breeze light, Breeze dark) can now be selected manually (Bart De Vries, KDE Gear 24.02 Link 2)

Network checks for metered connections can now be disabled altogether. This can be useful on systems that are not able to reliably report the connection status (Bart De Vries, KDE Gear 24.02 Link 3)

Hash-o-Matic

Hash-o-Matic is a new application that lets you verify the authenticity of files by using their MD5, SHA-256 and SHA-1 hashes or their PGP signature.

Hash-o-Matic also let you generate hash for a file and compare two files.

Contributing

Do you want to help with the development of Plasma Mobile? We are a group of volunteers doing this in our free time, and are desperately looking for new contributors, beginners are always welcome!

See our community page to get in touch!

We are always happy to get more helping hands, no matter what you want to do, but we especially need support in these areas:

• Telephony

• Camera support

• You can also check out our Plasma Mobile issue tracker for more details.

Even if you do not have a compatible phone or tablet, you can also help us out with application development, as you can easily do that from a desktop!

Of course, you can also help with other things besides coding! For example, take Plasma Mobile for a spin to help us test bugs and triage reports! Check out the device support for each distribution and find the version which will work on your phone.

Another option would be to help us in making these blog posts more regular again. We really don't want another 6 months of silence, but writing these take a surprising amount of time and effort.

If you have any further questions, view our documentation, and consider joining our Matrix channel. Let us know what you would like to work on or where you need support to get going!

Our issue tracker documentation also gives information on how and where to report issues.

On a final note...

We would like to thank all of the contributors across KDE that have made this megarelease possible! We could not have done it without you. Thank you!

We are happy to announce the release of Qt Creator 13 Beta2!

The robustness of Linux is widely acknowledged, but it can’t quite match the microsecond management of a real-time operating system (RTOS) for time critical situations such as CNC machine instructions, vehicular control, or health sensor collection. If your software must record, manage, or control events within a narrow and precise time window and you’re invested in Linux for core development, you can consider some of these strategies for handling time-critical tasks without abandoning your familiar environment.

Real-time patches

Linux can be nudged closer to real-time performance using kernel patches specifically designed for real-time applications like PREEMPT_RT. These patches modify the Linux kernel to reduce latency and improve the predictability of task scheduling by minimizing the duration of non-preemptible critical kernel code. This does not transform Linux into a hard real-time system, but it provides sufficient precision for many scenarios. Bear in mind that this solution requires you to keep your real-time patches aligned with your Linux kernel, which might slow down the frequency of kernel updates your team can manage. You also must navigate issues such as page swapping that can disrupt timing.

Embracing the hypervisor

Hypervisors offer a parallel environment beneath/beside Linux to manage time-sensitive tasks. They enable running virtual machines (VMs) alongside the main Linux system, each capable of hosting different operating systems. This allows you to place your real-time tasks into an RTOS while reserving Linux for higher-level functions. While hypervisors can improve real-time reliability and system flexibility, don’t forget to take their overhead and resource contention into account.

Onboard processing

Modern CPUs often feature integrated co-processors, like an ARM Cortex-M or a DSP, which is suitable for real-time operations as well as low-power needs while the main CPU is dormant. These can handle time-critical tasks independent of the CPU, effectively using available hardware resources without the need for additional components. These parallel processing environments can be highly efficient at specific tasks. However, this approach adds complexity in coordinating tasks and data flow between CPUs and co-processors – and not all hardware platforms have suitable co-processors.

Leverage a microcontroller

For dedicated time-critical processing, especially in low-power applications, microcontrollers can be very effective. With a basic event loop or interrupt-driven sleep mode, they operate efficiently and independently, offering high reliability as dedicated systems, and potentially lower power consumption for battery-powered devices. The drawback is that they can increase costs due to additional hardware, potentially create a larger physical footprint, and add development complexity because of separate code bases.

Dedicated cores

Reserving a CPU core exclusively for real-time tasks might be overkill, but it’s a viable option when there’s sufficiently extra processing power. By using cores optimized for lower power consumption, this method can also have power-saving benefits. A real-time dedicated core ensures that time-critical tasks don’t get interrupted by other system activities. However, it almost always underutilizes the processor’s full capabilities and can be complex to properly manage memory pages and core affinities.

Which solution is the best?

The appropriateness of these methods hinges entirely on the specifics of your time-critical hardware and access requirements. For instance, if essential hardware is only accessible via the main CPU, microcontrollers or co-processors won’t be viable. Implementing any of these solutions introduces complexity, often requiring dual software environments and toolsets, as well as solid communication between time-critical and non-critical processes (communication channels must be designed meticulously to avoid becoming performance bottlenecks).

Conclusion

Incorporating time-critical capabilities into Linux systems is a balancing act of innovation and practicality. While Linux may never achieve ‘hard’ real-time status, with care and innovation it can be adapted to meet time-sensitive demands. Integrating real-time capabilities into a Linux-based system is a multifaceted challenge and each solution presents a unique set of trade-offs. To learn more about these challenges and related topics, read Designing Your First Embedded Device: Choosing Your Software Stack.

About KDAB

If you like this article and want to read similar material, consider subscribing via our RSS feed.

Subscribe to KDAB TV for similar informative short video content.

KDAB provides market leading software consulting and development services and training in Qt, C++ and 3D/OpenGL. Contact us.

The post Punctuality Matters: Using Linux to Manage Time-Critical Situations appeared first on KDAB.

It’s February already, and as expected I didn’t have too much time on my hands this month. I have some exciting related news though:

KDE Megarelease 6 #

If you somehow haven’t heard, a bunch of KDE 6-related stuff released yesterday! I highly recommend looking at the very nice announcement Carl and the rest of the KDE Promo team put together, it looks so good. Some of my changes in KCMs, Kiten, UnifiedPush support in Tokodon & NeoChat, PlasmaTube, and Tokodon are showcased there 🤩 One of my favorite changes is probably in KWin and the Wayland session, it’s near-perfect on my machine now.

NLnet Grant #

For a while now, people have been asking about funding work on important Wayland features for artists and people who depend on accessibility features. We have been turning down offers from individual fundraisers, because behind the scenes my employer arranged a grant us to work on this task from NLnet! “Us” here means me and Nicolas Fella. I hope to begin in early April.

Tokodon #

Feature I changed the thread visuals to improve the readability of replies. Note that it’s only one level deep, but even with that limitation I find it to be way better than it was before! 24.05

Better thread visuals

Feature I did some neat notification changes, such as enabling group notifications by default and hiding the post actions unless required for notifications. The notifications page should have less visual noise now. 24.02.1

Less visual noise on the notifications page

Feature Tokodon now warns if replies may be hidden from your server and suggests to open the original post in your web browser. This isn’t the greatest solution yet, eventually I want a way to load the post on the original server within Tokodon. This is a good start though, instead of showing nothing. 24.05

The new replies message NeoChat #

Bugfix Rebased and cleaned up my bugfix to prevent editing messages destroying the formatting. This should be integrated soon!

Frameworks #

Bugfix Fixed my typo that caused KFileMetadata to fail when not building with KArchive support, oops! 6.1

Bugfix Add the missing and new Breeze icons dependency to kiconthemes. 6.1

My work in KDE for January 2024

My Work in KDE

Home

There are release parties around the world, the UK has a party in Cambridge.

Action plan is to go to The Haymakers, High Street, Cambridge and get pizza, drinks and more pizza. at 19:00 Thursday the 29th Feb.

Look for the guy in the blue KDE T-shirt.

Sign up at https://community.kde.org/Promo/Events/Parties/KDE_6th_Megarelease#Cambridge

Today KDE has made its biggest release ever, never before in the 25 year history of the project have we announced so many new products at the same time but it brings the newly refreshed base to keep our software foundation strong.

KDE neon User edition has now been updated with KDE Frameworks 6, Plasma 6 and all the apps from KDE Gear 24.02. You can upgrade through Discover or grab the newest installable ISO build.

If you just want to give it a try then give the Docker images a go.

Many thanks to Carlos, Harald and Jonathan for making this Neon release, to the 100s of KDE developers for writing the software and to Augustin and Paul for hosting the release sprint in Malaga.

Several versions of Qt have been released since my last treatise on QML modules. Most of it is in fact still very valid advice, but I feel I have to stress a few things that people often misunderstand.

Full content here: https://kde.org/announcements/megarelease/6

Today, we bring you a report on the brand-new release of the Maui Project.

We are excited to announce the latest release of MauiKit version 3.1.0, our comprehensive user interface toolkit specifically designed for convergent interfaces, the complying frameworks, an in-house developed set of convergent applications, and the upcoming convergent shell environment for desktop and mobile devices.

Built on the foundations of Qt Quick Controls, QML, and the power and stability of C++, MauiKit empowers developers to create adaptable and seamless user interfaces across a range of devices, and with this release, we are a step closer to finalizing the migration to a new major version – the upcoming MauiKit4 release.

Join us on this journey as we unveil the potential of MauiKit3 for building convergent interfaces, the roadmap towards MauiKit4 and its new additions, and finally discover the possibilities offered by the enhanced Maui App stack.

Community

To follow the Maui Project’s development or to just say hi, you can join us on Telegram @mauiproject

We are present on Twitter and Mastodon:

• https://twitter.com/maui_project
• https://floss.social/@mauiproject

Thanks to the KDE contributors who have helped to translate the Maui Apps and Frameworks!

Downloads & Sources

You can get the stable release packages [APKs, AppImage, TARs] directly from the KDE downloads server at https://download.kde.org/stable/maui/

All of the Maui repositories have the newly released branches and tags. You can get the sources right from the Maui group: https://invent.kde.org/maui

MauiKit4 & Documentation

MauiKit Calendar, Accounts, and Image Tools have now been ported to Qt6, joining MauiMan, MauiKit, and File Browsing frameworks. Alongside with the porting efforts, the frameworks are now documented, and available on the KDE API documentation site [HERE]. The remaining frameworks to be ported to Qt6 are MauiKit Terminal, Documents, and Text Editor, which should be fully ported and documented by the upcoming release in May.

The porting also involved updating the framework CMake code to the latest ECM changes introduced for creating QML plugins.

For the upcoming porting of MauiKit Text Editor, there are plans to move to a different backend for rendering the text more efficiently, and for Documents, the comics and ebooks backends will be reviewed and refactored to address crashing issues under Android.

You can find more information about the roadmap and plans for the migration to Qt6 at: https://invent.kde.org/maui/mauikit/-/issues/35

MauiKit Frameworks & Apps

A quick overview of the issues addressed and updates are covered in the following list:

• Updated translations and support for more languages
• Rebase MauiKit ApplicationWindow to QQC2 ApplicationWindow to resolve focus-stealing issues in Android
• Update all the applications’ source code syntax in QML for the upcoming Qt6 port
• Pick up the system light/dark preference for Android in MauiKit3, and move the handling of the Android status bar color from each app to MauiKit’s ApplicationWindow control. For MauiKit4 relay in the QStyleHints new properties
• Split the  MauiApp code from the CSDControls. Thus register CSDControls as a new attached property: Maui.CSD [link to docs]
• Expose the MauiKit Application root element via the attached property MauiApp, as Maui.App.rootComponent [link to docs]
• Station fixes for handling the “terminate-session” shortcut and fixes to crashing issues when closing tabs, coming from MauiKit Terminal
• The MauiKit’s PageLayout control has been backported from MauiKit4 to MauiKit3, and its implementation has gained new features, such as moving the collapsable elements to the footer. [link to docs]
• Index app is now using MauiKit’s PageLayout control for splitting the toolbar actions for constrained spaces, the same as Pix
• Pix fix the tags hot-reloading on new tags created
• Fixes to nota syncing the terminal working directory

https://mauikit.org/wp-content/uploads/2024/02/Peek-2024-02-13-11-53.mp4

• Vvave has gained a new option to quickly start a playlist in shuffle mode and a sleep timer: to stop playback and/or close the app after a certain time or end of the playlist
• MauiKit’s AboutDialog has been revised and organized
• MauiKit FileBrowsing control for creating a new file now picks the icon from the name extension
• MauiKit Terminal and Text Editor now have a custom control exposing configurations for selecting custom color schemes
• Index now has options to tweak the embedded terminal in Linux, such as custom color schemes, and reorganized setting entries for the terminal configurations
• Nota now reuses the new Text Editor control for picking the color scheme and new options for  tweaking the embedded terminal
• All of the apps now use an exported definition or the copyright notice
• Fixes for all of the apps where the names of developers and other non-translatable strings were being marked as such
• Fixed keyboard shortcuts for Station, Vvave, and other apps
• Added style for the ComboBox component
• MauiKit corrects the usage of singleton instances across threads for all the frameworks, which avoids the double instantiation from the CPP and QML side
• Fixes to MauiKit TextEditor long press actions on touch screens
• Fixes to style hints for the scrollbar policy coming from MauiMan
• Fixes to Nota’s recent view selection mode
• On mobile devices do not cache image or icon previews for the thumbnail delegates

[Known Bugs]

• Nota crashes when opening a new file from the recent view under Android.
• MauiKit Documents fails to open large comic books on Android, causing the app to crash due to the current design of using multiple threads for different pages. This is planned to be solved at MauiKitDocuments4 porting
• MauiKit Text Editor TextArea has a flickering issue, which makes content jumpy on Android only. This is from upstream and should be solved on MauiKitTextEditor4 porting when moving to a different backend.
• MauiKit FileBrowsing support for browsing SD cards on Android is currently disabled due to missing bindings to the “new” Android storage API

[What’s Next?]

For the next release, we plan to work on stabilizing the Maui Shell experience, by adding  XWayland support, and a few more things:

• Finalize the porting of the MauiKit Frameworks to Qt6
• Finalize and review the MauiKit documentation
• Start the porting process of the Maui Apps to MauiKit4 AKA Qt6
• Review MauiKit4 on Android
• Review the migration of TextEditor to a new backend
• Fixes to bugs on the Maui Apps stack
• Update the Maui Apps features that are still pending

 

Maui Shell

For this release, Maui Shell and its components have received minimal updates coming from:

• MauiCore and Maui Settings new modules for Audio and Network
• Updated Maui Settings for MauiKit4 changes
• Review shell aka Cask elements to be up to date with the MauiKit4 changes

 

That’s it for now. Until the next blog post, that will be a bit closer to the 3.1.1 stable release.

To follow the Maui Project’s development or say hi, you can join us on Telegram: https://t.me/mauiproject.

We are present on Twitter and Mastodon:

• https://twitter.com/maui_project.
• https://mastodon.technology/@mauiproject.

New release schedule

The post Maui Release Briefing #5 appeared first on MauiKit — #UIFramework.

You may have already read about it on Volkers blog: we together with people from other public transport related projects are building a public transport routing service called Transitous. While of course our main motivation is to use it in KDE Itinerary, KDE’s travel planning app, it will be open for use in other apps.

We also have a little web interface running at transitous.org.

We are building this service based on great existing software, in particularly MOTIS.

Now, to make this really useful, we need data on more regions. Luckily, for most regions and countries that is fairly easy. Most transport agencies and countries make GTFS feeds available, that we can just use.

Adding an additional feed doesn’t take long and doesn’t need programming experience. It’s pretty much just creating a small text file that explains how and where to download the data from.

Those links don’t necessarily stay the same forever, so we would be happy if lots of people take care of their region, and update the link every few years. It is really little work if split up, but can’t all be handled by a small team.

To make it even easier, we can already use the Transitland Atlas feed collection, for which you just need to choose the feed to use. The url will then automatically be looked up.

You can find out how to add a feed here. Please let us know if the documentation is unclear anywhere.

If you are interested in using this service in your own application, it is probably a bit too early for production, but it makes sense to already implement support for the MOTIS API that we use. You can find an early version of our API documentation here.

If there is anything else you are interested in helping with, for example improving our ansible playbook, creating a website, improving MOTIS or working on integrating OpenStreetMap routing, you can find our open tasks here. We appreciate any help on those issues, and it of course speeds up the development of the project.

Plasma Pass is a Plasma applet for the Pass password manager

This release includes build fixes for Plasma 6, due to be released later this week.

URL: https://download.kde.org/stable/plasma-pass/
Sha256: 2a726455084d7806fe78bc8aa6222a44f328b6063479f8b7afc3692e18c397ce
Signed by E0A3EB202F8E57528E13E72FD7574483BB57B18D Jonathan Esk-Riddell <jr@jriddell.org>
https://jriddell.org/esk-riddell.gpg

It’s high tension in Neon towers this week as the distro packagers have been given access to the source tars for Plasma 6 along with Frameworks 6 and KDE Gear 24.02. This means our cloud of build servers have been powered up to compile them into .deb packages which go into our Apt archive. In principle we already have the packaging working in Unstable and Testing edition so it should be a case of just doing a fresh build in User edition but it involves several hundred source builds all done for the three editions and for libraries and plugins (such as KIO Workers) many of them twice over, once for Qt 6 and once for Qt 5 builds. So lots of bits which need aligned. Frameworks completed yesterday morning and this morning it looks like all of Plasma is built. The KDE Gear apps are churning away now. We’ll then need to tests it all including many configurations of upgrade to make sure it doesn’t break your laptops. The releases are due on Wednesday and with any luck we will have Neon builds available very shortly after, but of course we’ll wait until it’s ready if that’s what we have to do. It’ll be just a normal upgrade available to Discover but of course with a large number of packages to download. Who’s excited?

Welp, the mega-release is pretty much carved in stone now, and set for a release in four days! Lots of people have worked really hard on it for over a year, and we hope you love it! Nevertheless, I’m sure our diligent QA-obsessed users will waste no time in finding all the issues we missed, and we’ll work as hard as we can to fix them.

But once those are fixed too, the focus will eventually begin to shift once more towards features. And we have big ideas for new features to ship in Plasma 6.1 and beyond! With the architectural work done over the past year, a lot of very exciting possibilities have been unlocked. I think we’re going to see Plasma 6 as a pretty amazing springboard for next-gen stuff very quickly.

And to start things off, we have two nice new features that are landing in Plasma 6.1 already:

New Features

Even though we don’t have real session restore on Wayland yet (it’s still waiting for the protocol to be finalized), now we have the next best thing: fake session restore that simply re-opens apps you had open at the last logout and relies on them to have internally saved their own state appropriately. This works on X11 too (where apps that remember their window positions can do that as well), and it applies to all windows not covered by real session restore. As a result, now all your apps should always re-launch properly on login, rather than only the random-seeing assortment of session-restore-supporting apps re-launching on login. This feature is controlled by the existing setting that turns on or off session restore (David Edmundson, Plasma 6.1. Link)

In the Overview and Present windows effect, the way that windows are arranged is no longer configurable between two imperfect options: now there is only one layout algorithm and it’s waaaaaaay better than the old one! Windows are now arranged much more regularly and it ditches the very haphazard feeling of the old default algorithm, fixing multiple bugs causing weird window layouts including the infamous “stairway to heaven” arrangement (Yifan Zhu, Plasma 6.1. Link 1, link 2, link 3, link 4, link 5):

UI Improvements

When dragging a file or folder over another folder in Dolphin with the option turned on that opens the folder if you hold the dragged file there for a moment, the hovered folder now displays a little animation showing it open a bit (Felix Ernst, Dolphin 24.05. Link):

https://i.imgur.com/ZSZRoN2.mp4

Headsets that report their battery status properly now benefit from a nice icon in all the places in Plasma that can show battery status (Severin Von Wnuck-Lipinski Plasma 6.1. Link)

The desktop context menu has lost its “Refresh” action which was infrequently used and did not actually fix most problems of missing icons that people might want to use it for. This makes the context menu lean and mean, and now nobody will have reason to say it’s “bloated” ever again! You can still manually refresh with F5 if needed (me: Nate Graham, Plasma 6.1. Link):

Bug Fixes

When connecting an iPhone or other Apple mobile device to your machine using a cable, and that phone has a name with an apostrophe in it (e.g. “Konqi’s iPhone”), now it works (Kai Uwe Broulik, kio-extras 24.02. Link)

Fixed the most common KWin crash on X11, which was commonly seen when the screen arrangement changed (Xaver Hugl, Plasma 5.27.11. Link)

Changing the Address, Name Style, Paper Size, or Phone Numbers settings on System Settings’ Region & Language page now actually takes effect (Timo Velten, Plasma 5.27.11. Link)

Fixed an issue that could cause the screen to turn black with only a movable cursor after switching from one virtual terminal to another one with certain graphics hardware (Jakob Petsovits, Plasma 5.27.11. Link)

Wind speed is now properly refreshed over time in forecasts provided by EnvCan in the Weather widget (Ismael Asensio, Plasma 5.27.11. Link)

Fixed a bug that could causing dragging-and-dropping Task manager icons to sometimes stop working (Fushan Wen, Plasma 6.0. Link)

KWin’s Zoom effect can now fully zoom into all areas of complex multi-screen setups (Michael VanOverbeek, KWin 6.0. Link)

A process named “ksmserver-logout-greeter” no longer shows up in your Task Manager while the logout screen is visible (Akseli Lahtinen, Plasma 6.0. Link)

Fixed a visual glitch that could cause window outlines to become slightly disconnected from their windows at certain window sizes when using certain fractional scale factors (Akseli Lahtinen, Plasma 6.0.1 Link)

Fixed a visual glitch that could cause windows on rotated displays to be briefly rotated incorrectly after becoming visible when using the “Glide” effect (Vlad Zahorodnii, Plasma 6.0.1. Link)

Fixed a case where KWin could crash when using the relatively old 340-series of NVIDIA drivers (Vlad Zahorodnii, Plasma 6.0.1. Link)

Fixed a way that Plasma could crash when manually restarted using systemd (Harald Sitter, Plasma 6.1. Link)

The shortcut chooser in the panel configuration dialog now respects your Plasma style’s color scheme as expected (Marco Martin, Frameworks 6.0. Link)

Toast-style notifications sent by Kirigami-based apps no longer visually overflow when they have a large amount of text in them (Jack Hill, Frameworks 6.0. Link)

Other bug information of note:

• 3 Very high priority Plasma bugs (same as last week). Current list of bugs
• 30 15-minute Plasma bugs (same as last week). Current list of bugs
• 169 KDE bugs of all kinds fixed over last week. Full list of bugs

Performance & Technical

Improved Dolphin’s startup time by between 2% and 17% (Felix Ernst, Dolphin 24.05. Link)

Automation & Systematization

Added an autotest to ensure the proper functionality of text field context menus in QtQuick-based software (Fushan Wen, link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an amazing 850 members. Thank you everyone for the confidence you’ve shown in us; we’ll try not to screw it up! For those who haven’t donated to become members yet, spreading the wealth via this fundraiser is a great way to share the love.

If you’re a developer… sheesh, take a break for a few days. You’ve earned it!

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

Just in time for KDE Plasma 6, Chromium 122 and Electron 29 have been released! They contain my patch that adds support for Wayland’s new cursor-shape-v1 extension protocol. When running natively in a Plasma 6 Wayland session, up-to-date Chromium-based browsers and Electron apps should now always use the correct mouse cursor theme and have the...

The post cursor-shape-v1 in Chromium and Electron first appeared on Ilya's Blog.