Language Selection

English French German Italian Portuguese Spanish

KDE Frameworks 5.55 Released for KDE Plasma 5.15, Improves Android Notifications

Filed under
KDE

Just in time for the February 12 release of the highly anticipated KDE Plasma 5.15 desktop environment, the KDE Frameworks 5.55.0 open-source software suite is now available with dozens of improvements, updates, new features, and countless bug fixes. First and foremost, the Breeze icon theme received lots of new icons, so you should see a pleasing refresh after updating your KDE Plasma desktop to KDE Frameworks 5.55.

Moreover, the exiv2extractor utility received support for BMP, GIF, WebP, and TGA image formats, taglibwriter received support for additional mimetypes, the KIconThemes, KService, KXMLGUI, and Solid components are now built without D-Bus on Android, KNotification received Android notification channel support and support for Android API level < 23, and KTextEditor got a bunch of improvements too.

Read more

Also: KDE Frameworks 5.55 Released With Android Notifications, KWayland Fixes

More in Tux Machines

FreeBSD Quarterly Status Report

We also provide some up to date information about the status of our IRC channels Read more Also: FreeBSD In Q2'2019 Saw Updated Graphics Drivers, Continued Linux Compatibility Layer

DragonFlyBSD Pulls In AMD Radeon Graphics Code From Linux The 4.7 Kernel

It was just last month that DragonFlyBSD pulled in Radeon's Linux 4.4 kernel driver code as an upgrade from the Linux 3.19 era code they had been using for their open-source AMD graphics support. This week that's now up to a Linux 4.7 era port. François Tigeot who continues doing amazing work on pulling in updates to DragonFlyBSD's graphics driver now upgraded the Radeon DRM code to match that of what is found in the upstream Linux 4.7.10 kernel. Read more

Android Leftovers

TenFourFox FPR16b1 available

FPR16 got delayed because I really tried very hard to make some progress on our two biggest JavaScript deficiencies, the infamous issues 521 (async and await) and 533 (this is undefined). Unfortunately, not only did I make little progress on either, but the speculative fix I tried for issue 533 turned out to be the patch that unsettled the optimized build and had to be backed out. There is some partial work on issue 521, though, including a fully working parser patch. The problem is plumbing this into the browser runtime which is ripe for all kinds of regressions and is not currently implemented (instead, for compatibility, async functions get turned into a bytecode of null throw null return, essentially making any call to an async function throw an exception because it wouldn't have worked in the first place). This wouldn't seem very useful except that effectively what the whole shebang does is convert a compile-time error into a runtime warning, such that other functions that previously might not have been able to load because of the error can now be parsed and hopefully run. With luck this should improve the functionality of sites using these functions even if everything still doesn't fully work, as a down payment hopefully on a future implementation. It may not be technically possible but it's a start. Read more