Language Selection

English French German Italian Portuguese Spanish

Plasma 5.16 by KDE is Now Available

Filed under
KDE

Say hello to Plasma 5.16, a the newest iteration of KDE's desktop environment, chock-a-block with new features and improvements.

Let’s start with Dolphin, Plasma's file and folder manager. It now opens folders you click on in new tabs instead of new windows, keeping everything together. You can try this out by clicking the Home folder icon on your desktop (which will open Dolphin and show the contents of Home), and then clicking the Trash can folder also on your desktop. The Trash can folder will open in a new tab of the existing Dolphin window. You can, of course, choose to open more than one Dolphin window -- after all, it wouldn't be Plasma without options -- but this is a feature that will keep things nice and tidy.

Talking about tidy: check out the new notification system! Not only can you mute notifications altogether with the Do Not Disturb mode, but the system also groups notifications by app. Like this, when you run through the history of past notifications, you can see all the messages from KDE Connect in one category, the download information in another, email alerts in a third, and so on.

Discover, Plasma's software manager, is also cleaner and clearer as it now has two distinct areas for downloading and installing software on the Update page. Besides, when updating, the completion bar now works correctly and the packages disappear from the list as the software manager completes their installation.

Read more

By Marius Nestor shortly after the original

  • KDE Plasma 5.16 Desktop Environment Officially Released, Here's What's New

    The KDE Project released today the KDE Plasma 5.16 desktop environment, a major release that adds a plethora of new features and enhancements, along with many improvements to make your Plasma experience more enjoyable and reliable.
    The KDE Plasma 5.16 has been in development for the past few months and it's now the latest version of the acclaimed graphical desktop environment for Linux-based operating systems. It's a major release that introduces several new features, more polishing, and dozens of improvements.

    "For this release, KDE developers have worked hard to polish Plasma to a high gloss. The results of their efforts provide a more consistent experience and bring new features to all Plasma users," reads today's announcement. "We hope you enjoy using Plasma 5.16 as much as we did making it."

KDE Plasma 5.16 Released With A Lot Of Polishing

  • KDE Plasma 5.16 Released With A Lot Of Polishing, File Manager Improvements

    KDE Plasma 5.16 is out today as the latest major update to the modern KDE desktop.

    KDE Plasma 5.16.0 brings with it a rewritten notification system, KWin fixes, DPI scaling fixes, NVIDIA EGLStreams support, a NVIDIA CPU usage fix, restoring the option to reboot into the UEFI settings, WireGuard support, Dolphin file manager improvements, and much more.

KDE Plasma 5.16 Desktop Is Now Available for Kubuntu...

  • KDE Plasma 5.16 Desktop Is Now Available for Kubuntu and Ubuntu 19.04 Users

    KDE Plasma 5.16 launched earlier today as the latest and most advanced version of the acclaimed graphical desktop environment for Linux-based operating systems, adding several new features and enhancements like a totally revamped notifications system, improved System Settings pages, and revamped login, logout, and lock screens.

    The KDE Plasma 5.16 release also brings better support for Wayland when using the Nvidia proprietary graphics drivers, improved networking, a much easier to use Plasma Discover graphical software manager, and a much-improved overall desktop experience with lots of polishing for themes, color schemes, widgets, and the panel.

Kubuntu and Neon

  • Plasma 5.16 for Disco 19.04 available in Backports PPA

    We are pleased to announce that Plasma 5.16, is now available in our backports PPA for Disco 19.04.

    The release announcement detailing the new features and improvements in Plasma 5.16 can be found here

    Released along with this new version of Plasma is an update to KDE Frameworks 5.58. (5.59 will soon be in testing for Eoan 19.10 and may follow in the next few weeks.)

  • KDE neon 5.16 Out

    KDE neon 5.16 is out featuring Plasma 5.16. Download the ISO now or upgrade your installs.

    With Diversity in mind this edition features an Ice Cold themed wallpaper to make those in the southern hemisphere feel included.

Official Release Announcement

  • Release Announcements: Plasma 5.16.0

    Today KDE launches the latest version of its desktop environment, Plasma 5.16.

    For this release, KDE developers have worked hard to polish Plasma to a high gloss. The results of their efforts provide a more consistent experience and bring new features to all Plasma users.

    One of the most obvious changes is the completely rewritten notification system that comes with a Do Not Disturb mode, a more intelligent history which groups notifications together, and critical notifications in fullscreen apps. Besides many other things, it features better notifications for file transfer jobs, and a much more usable System Settings page to configure all notification-related things.

Plasma 5.16 is now available for Disco 19.04 from Backports PPA

  • Plasma 5.16 is now available for Disco 19.04 from Backports PPA

    Plasma 5.16 is now available for Disco 19.04 from Backports PPA

    KDE community have launched the latest version of its desktop environment, Plasma 5.16 on 11 June, 2019.

    At the same time kubuntu developers has announced the Plasma 5.16 is now available from their backports PPA for Disco 19.04.

    Released along with this new version of Plasma is an update to KDE Frameworks 5.58.

KDE Plasma 5.16 Released – And It’s a Big One!

  • KDE Plasma 5.16 Released – And It’s a Big One!

    So what’s new? Well, what isn’t!? Plasma 5.16 is chock-full of changes, improvements and little flourishes that, together, create an impressive whole.

    KDE devs say they “…worked hard to polish Plasma to a high gloss. The results […] provide a more consistent experience and bring new features to all Plasma users.”

    And based on the surfeit of screenshots they’ve provided, i’d dare say they succeeded!

    Chances are you want to learn more, so let’s dive in!

KDE Plasma 5.16 Brings Glossy Improvements

  • KDE Plasma 5.16 Brings Glossy Improvements

    KDE announced the release of its desktop environment, Plasma 5.16. This major release brings some important changes in user interface, widgets, notifications and many areas. KDE Plasma was in development for past few months and as a result of that we have the glossy and shiny Plasma 5.16 desktop environment.

    “For this release, KDE developers have worked hard to polish Plasma to a high gloss. The results of their efforts provide a more consistent experience and bring new features to all Plasma users. We hope you enjoy using Plasma 5.16 as much as we did making it.” – as quoted from the official announcement.

What is new in KDE Plasma 5.16

June installment of KDE Plasma5 for Slackware, includes Plasma 5

  • June installment of KDE Plasma5 for Slackware, includes Plasma 5.16

    Sometimes, stuff just works without getting into kinks. That’s how I would like to describe the June release of Plasma5 for Slackware, KDE-5_19.06.

    I built new Plasma5 packages in less than two days. I did not run into build issues, there was no need for a bug hunt. The Ryzen compiled and compiled, and then the power went out in the building today… but still, moments ago I uploaded KDE-5_19.06 to my ‘ktown‘ repository. As always, these packages are meant to be installed on a full installation of Slackware-current which has had its KDE4 removed first. These packages will not work on Slackware 14.2.

KDE launches the latest version of its desktop environment

  • KDE launches the latest version of its desktop environment, Plasma 5.16

    Plasma 5.16 comes with a rewritten notification system. With Do Not Disturb mode, you can mute notifications, and the list of previous notifications now shows them grouped by app. Critical notifications appear even when applications are in fullscreen mode.

    In addition, this release adds the much-awaited feature to display notifications for file transfer jobs. System Settings app allows you to configure everything related to notifications.

    Following the footsteps of most of Linux distros development, the standard wallpaper of Plasma 5.16 was chosen for the first time through a competition that everyone could participate and present their original art. The winning wallpaper – the work of an Argentinian talented artist.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Fedora Workstation 31, AAC Support

  • Fedora Workstation 31 to come with Wayland support, improved core features of PipeWire, and more

    On Monday, Christian F.K. Schaller, Senior Manager for Desktop at Red Hat, shared a blog post that outlined the various improvements and features coming in Fedora Workstation 31. These include Wayland improvements, more PipeWire functionality, continued improvements around Flatpak, Fleet Commander, and more.

  • Fedora's AAC Support Finally Seeing Audio Quality Improvements

    Fedora's version of the FDK-AAC library that they began shipping in 2017 to finally provide AAC audio support strips out what was patented encumbered functionality. But that gutting of the code did cause some problems like audio playback glitches that are now being addressed. Fortunately, better AAC support is on the way to Fedora. There is this F30 update pending to provide an updated AAC implementation with quality enhancements.

Mozilla: Firefox's Gecko Media Plugin & EME Architecture, Accessibility, Firefox 68 Beta 10 Testday Results

  • Chris Pearce: Firefox's Gecko Media Plugin & EME Architecture

    For rendering audio and video Firefox typically uses either the operating system's audio/video codecs or bundled software codec libraries, but for DRM video playback (like Netflix, Amazon Prime Video, and the like) and WebRTC video calls using baseline H.264 video, Firefox relies on Gecko Media Plugins, or GMPs for short. This blog post describes the architecture of the Gecko Media Plugin system in Firefox, and the major class/objects involved, as it looked in June 2019. For DRM video Firefox relies upon Google's Widevine Content Decryption Module, a dynamic shared library downloaded at runtime. Although this plugin doesn't conform to the GMP ABI, we provide an adapter to allow it to be run through the GMP system. We use the same Widevine CDM plugin that Chrome uses. For decode and encode of H.264 streams for WebRTC, Firefox uses OpenH264, which is provided by Cisco. This plugin implements the GMP ABI.

  • Hacks.Mozilla.Org: How accessibility trees inform assistive tech

    The web is accessible by default. It was designed with features to make accessibility possible, and these have been part of the platform pretty much from the beginning. In recent times, inspectable accessibility trees have made it easier to see how things work in practice. In this post we’ll look at how “good” client-side code (HTML, CSS and JavaScript) improves the experience of users of assistive technologies, and how we can use accessibility trees to help verify our work on the user experience.

  • QMO: Firefox 68 Beta 10 Testday Results

    As you may already know, Friday June 14th – we held a new Testday event, for Firefox 68 Beta 10.

Security Leftovers/FUD

  • New Linux Worm Attacks IoT Devices [Ed: How to blame "Linux" for default passwords in devices (and some now also blame "Iran", citing a CIA 'proxy' Recorded Future in relation to this because they want war)]

    Silex has 'bricked' more than 2000 Linux-based IoT devices so far.

  • Your server remote login isn't root:password, right? Cool. You can keep your data. Oh sh... your IoT gear, though? [Ed: All this "Silex" 'news' tries to blame Iran for cracking by guessing default passwords; but this is attempted every day by dozens of nations, every minute in a lot of cases. Any political motivation behind this Iran angle?]

    Earlier this week, infosec outfit Recorded Future claimed a Tehran-backed group known as Elfin, or APT33, has been increasingly active in recent months, largely targeting industrial facilities and companies within Saudi Arabia that do business with the US and other Western countries.
  • 'Silex' Malware Renders Internet-of-Things Devices Useless. Here's How to Prevent It [Ed: War lovers' media, e.g. Fortune (see parent) and CBS (through ZDNet) push this whole "Iran" angle, manufactured in part by Recorded Future, which works with the CIA. This is the source of all these "Iran is cracking your gear" stories (every large nation does it all the time, so why the focus on Iran all of a sudden?)]
  • Silex malware targeting IoT devices spotted by security researchers
  • Daily News Roundup: Hackers Broke into Ten Telecom Networks [Ed: Definitely sounds like they used Windows, which executes malware without obstructing the users (who might just open an E-mail or click on a link)]

    Security researchers have revealed hackers spent years burrowing into ten different telecoms. Using a common method of an email with a link leading to malware, the hackers then used sophisticated techniques to target specific individuals. Security researchers at Cybereason revealed details of years-long attempts to break into telecom services (cell phone carriers). Starting in 2017, and possibly before, hackers sent emails to unsuspecting telecom employees with malicious links. The initial payload gave the hackers access to the telecom networks. Once in, the hackers ultimately compromised the network, gaining administrative privileges, and even creating a VPN on the system that let hackers access large amounts of data and empowered them even to shut down the telecom network entirely. The hackers had so much power that Amit Serper, Principal Security Researcher at Cybereason, described them as essentially a “de facto shadow IT department of the company.”

Kernel: LWN's Latest (SACK etc.) and Phoronix on Saitek R440 Force Racing Wheel Support Coming to Linux

  • The TCP SACK panic

    Selective acknowledgment (SACK) is a technique used by TCP to help alleviate congestion that can arise due to the retransmission of dropped packets. It allows the endpoints to describe which pieces of the data they have received, so that only the missing pieces need to be retransmitted. However, a bug was recently found in the Linux implementation of SACK that allows remote attackers to panic the system by sending crafted SACK information. Data sent via TCP is broken up into multiple segments based on the maximum segment size (MSS) specified by the other endpoint—or some other network hardware in the path it traversed. Those segments are transmitted to that endpoint, which acknowledges that it has received them. Originally, those acknowledgments (ACKs) could only indicate that it had received segments up to the first gap; so if one early segment was lost (e.g. dropped due to congestion), the endpoint could only ACK those up to the lost one. The originating endpoint would have to retransmit many segments that had actually been received in order to ensure the data gets there; the status of the later segments is unknown, so they have to be resent. In simplified form, sender A might send segments 20-50, with segments 23 and 37 getting dropped along the way. Receiver B can only ACK segments 20-22, so A must send 23-50 again. As might be guessed, if the link is congested such that segments are being dropped, sending a bunch of potentially redundant traffic is not going to help things.

  • Short waits with umwait

    If a user-space process needs to wait for some event to happen, there is a whole range of mechanisms provided by the kernel to make that easy. But calling into the kernel tends not to work well for the shortest of waits — those measured in small numbers of microseconds. For delays of this magnitude, developers often resort to busy loops, which have a much smaller potential for turning a small delay into a larger one. Needless to say, busy waiting has its own disadvantages, so Intel has come up with a set of instructions to support short delays. A patch set from Fenghua Yu to support these instructions is currently working its way through the review process. The problem with busy waiting, of course, is that it occupies the processor with work that is even more useless than cryptocoin mining. It generates heat and uses power to no useful end. On hyperthreaded CPUs, a busy-waiting process could prevent the sibling thread from running and doing something of actual value. For all of these reasons, it would be a lot nicer to ask the CPU to simply wait for a brief period until something interesting happens. To that end, Intel is providing three new instructions. umonitor provides an address and a size to the CPU, informing it that the currently running application is interested in any writes to that range of memory. A umwait instruction tells the processor to stop executing until such a write occurs; the CPU is free to go into a low-power state or switch to a hyperthreaded sibling during that time. This instruction provides a timeout value in a pair of registers; the CPU will only wait until the timestamp counter (TSC) value exceeds the given timeout value. For code that is only interested in the timeout aspect, the tpause instruction will stop execution without monitoring any addresses.

  • Dueling memory-management performance regressions

    The 2019 Linux Storage, Filesystem, and Memory-Management Summit included a detailed discussion about a memory-management fix that addressed one performance regression while causing another. That fix, which was promptly reverted, is still believed by most memory-management developers to implement the correct behavior, so a patch posted by Andrea Arcangeli in early May has relatively broad support. That patch remains unapplied as of this writing, but the discussion surrounding it has continued at a slow pace over the last month. Memory-management subsystem maintainer Andrew Morton is faced with a choice: which performance regression is more important? The behavior in question relates to the intersection of transparent huge pages and NUMA policy. Ever since this commit from Aneesh Kumar in 2015, the kernel will, for memory areas where madvise(MADV_HUGEPAGE) has been called, attempt to allocate huge pages exclusively on the current NUMA node. It turns out that the kernel will try so hard that it will go into aggressive reclaim and compaction on that node, forcing out other pages, even if free memory exists on other nodes in the system. In essence, enabling transparent huge pages for a range of memory has become an equivalent to binding that memory to a single NUMA node. The result, as observed by many, can be severe swap storms and a dramatic loss of performance. In an attempt to fix this problem, Arcangeli applied a patch in November 2018 that loosened the tight binding to the current node. But, it turned out, some workloads want that binding behavior. Local huge pages will perform better than huge pages on a remote node; even local small pages tend to be better than remote huge pages. For some tasks, the performance penalty for using remote pages is high enough that it is worth going to great lengths — even enduring a swap storm at application startup — to avoid it. No such workload has been publicly posted, but the patch was reverted by David Rientjes in December after a huge discussion.

  • Rebasing and merging in kernel repositories

    What follows is a kernel document I have been working on for the last month in the hope of reducing the number of subsystem maintainers who run into trouble during the merge window. If all goes according to plan, this text will show up in 5.3 as Documentation/maintainer/rebasing-and-merging.txt. On the off chance that some potentially interested readers might not be monitoring additions to the nascent kernel maintainer's handbook, I'm publishing the text here as well. Maintaining a subsystem, as a general rule, requires a familiarity with the Git source-code management system. Git is a powerful tool with a lot of features; as is often the case with such tools, there are right and wrong ways to use those features. This document looks in particular at the use of rebasing and merging. Maintainers often get in trouble when they use those tools incorrectly, but avoiding problems is not actually all that hard. One thing to be aware of in general is that, unlike many other projects, the kernel community is not scared by seeing merge commits in its development history. Indeed, given the scale of the project, avoiding merges would be nearly impossible. Some problems encountered by maintainers result from a desire to avoid merges, while others come from merging a little too often.

  • Years Late But Saitek R440 Force Racing Wheel Support Is On The Way For Linux

    If you happen to have a Saitek R440 Force Wheel or looking to purchase a cheap and used racing wheel for enjoying the various Linux racing game ports or even the number of games working under Steam Play like F1 2018 and DiRT Rally 2.0, Linux support is on the way. The Saitek R440 Force Wheel can still be found from the likes of eBay for those wanting a cheap/used PC game racing wheel. Now coming soon to the Linux kernel is support for this once popular gaming wheel -- which was originally released back in 2004. The Linux kernel patch originally adding the Saitek R440 was sent last year only to be resent out recently in an attempt for mainline acceptance.