Language Selection

English French German Italian Portuguese Spanish

KDE:Amarok 2.9 Released, Qt for WebAssembly, KaOS 2018.01, KDE Discover, Skrooge 2.12.0, Krita 4.1, GTK Global Menu

Filed under
KDE
  • Amarok 2.9 Released As The Last Step Before Qt5/KF5

    The KDE developers working on the Amarok music player released version 2.9.0 this week as their last expected release atop the aging KDE 4 libraries and Qt4.

  • Amarok 2.9.0 "Hibernaculum" released

    As it may be customary for the upcoming season the Amarok team did some spring cleaning and is proud to announce the immediate release of Amarok 2.9.0. While we realize that the clock has run out on KDELibs 4 and Qt 4, we wanted to bring 20+ bug fixes from 18 contributors to our users before the next major release will harness all the shiny new things provided by Qt 5 and KDE Frameworks 5. In fact, the port is already progressing nicely in the Git 'kf5' branch, which is soon to become the new ‘master’ branch. We welcome everybody willing to help out to check out the source code and improve the next major version of Amarok!

  • [Development] Qt for WebAssembly

    As you may have noticed work on Qt for WebAssembly is underway. W

  • Qt Developers Begin Brewing Their WebAssembly Plans

    The Qt Company developers are soliciting feedback from developers and the community about what they would like to see out of WebAssembly support for the tool-kit.

    WebAssembly is now supported by all major web browsers as a binary format for allowing sandboxed executable code in web pages that is nearly as fast as native machine code. Many different projects are figuring out how to make use of WASM or offer support for it moving forward, including the Qt tool-kit.

  • What’s New in KaOS 2018.01

    KaOS 2018.01 is the latest release of KDE-focused Linux distro, KaoS Linux. This release features latest packages for the Plasma Desktop, includes Frameworks 5.42.0, Plasma 5.11.5, KDE Applications 17.12.1. All built on Qt 5.10.0. Also ships ships with an alternative desktop enviornment to KDE Plasma, called Liquidshell, which is a lightweight environment that’s still in development at the moment of writing.

    Powered by the latest Linux 4.14.14 kernel built with Retpoline support, Intel and AMD microcode firmware updates are also present. KaOS 2018.01 also ships with LLVM/Clang 5.0.1, Boost 1.66.0, ICU 60.2, Protobuf 3.5.1, Glib2 2.54.3, Libcdio 2.0.0, OpenCV 3.4.0, Ruby 2.5.0, and the Calamares graphical installer framework 3.2, which features experimental LVM support.

  • This week in Discover, part 9

    We need your help! Consider becoming a KDE contributor, and help make Discover the best Linux app store in existence!

  • Skrooge 2.12.0 released

    The Skrooge Team announces the release 2.12.0 version of its popular Personal Finances Manager based on KDE Frameworks.

  • More comics management: making proper ACBF files.

    Krita 4.1’s comic project management tools now support 90% of all ACBF features.

  • KDE Plasma 5.13 Getting GTK Global Menu Support

    For those relying upon GTK applications like LibreOffice, GIMP, and GNOME programs from the KDE desktop, the integration is taking a step forward with Plasma 5.13.

  • GTK Global Menu

    For the past couple of weeks I have been working on a way to get GTK applications talk to Plasma’s Global Menu feature. I came up with a little helper application called gmenu-dbusmenu-proxy that talks both GMenu and DBusMenu protocols. This way no adjustment on Plasma’s side is needed, it just sees a regular global menu enabled application.

More in Tux Machines

The Last Independent Mobile OS

The year was 2010 and the future of mobile computing was looking bright. The iPhone was barely three years old, Google’s Android had yet to swallow the smartphone market whole, and half a dozen alternative mobile operating systems—many of which were devoutly open source—were preparing for launch. Eight years on, you probably haven’t even heard of most of these alternative mobile operating systems, much less use them. Today, Android and iOS dominate the global smartphone market and account for 99.9 percent of mobile operating systems. Even Microsoft and Blackberry, longtime players in the mobile space with massive revenue streams, have all but left the space. Then there’s Jolla, the small Finnish tech company behind Sailfish OS, which it bills as the “last independent alternative mobile operating system.” Jolla has had to walk itself back from the edge of destruction several times over the course of its seven year existence, and each time it has emerged battered, but more determined than ever to carve out a spot in the world for a truly independent, open source mobile operating system. After years of failed product launches, lackluster user growth, and supply chain fiascoes, it’s only been in the last few months that things finally seem to be turning to Jolla’s favor. Over the past two years the company has rode the wave of anti-Google sentiment outside the US and inked deals with large foreign companies that want to turn Sailfish into a household name. Despite the recent success, Jolla is far from being a major player in the mobile market. And yet it also still exists, which is more than can be said of every other would-be alternative mobile OS company. Read more

How I Quit Apple, Microsoft, Google, Facebook, and Amazon

It was just before closing time at a Verizon store in Bushwick, New York last May when I burst through the door, sweaty and exasperated. I had just sprinted—okay I walked, but briskly—from another Verizon outlet a few blocks away in the hopes I’d make it before they closed shop for the night. I was looking for a SIM card that would fit a refurbished 2012 Samsung Galaxy S3 that I had recently purchased on eBay, but the previous three Verizon stores I visited didn’t have any chips that would fit such an old model. When I explained my predicament to the salesperson, he laughed in my face. “You want to switch from you current phone to an... S3?” he asked incredulously. I explained my situation. I was about to embark on a month without intentionally using any services or products produced by the so-called “Big Five” tech companies: Amazon, Apple, Facebook, Google, and Microsoft. At that point I had found adequate, open source replacements for most of the services offered by these companies, but ditching the Android OS, which is developed by Google, was proving difficult. Most of the tech I use on a day-to-day basis is pretty utilitarian. At the time I was using a cheap ASUS laptop at work and a homebrew PC at my apartment. My phone was a Verizon-specific version of the Samsung Galaxy J3, a 2016 model that cost a little over $100 new. They weren't fancy, but they’ve reliably met most of my needs for years. For the past week and a half I had spent most of my evenings trying to port an independent mobile OS called Sailfish onto my phone without any luck. As it turned out, Verizon had locked the bootloader on my phone model, which is so obscure that no one in the vibrant Android hacking community had dedicated much time to figuring out a workaround. If I wanted to use Sailfish, I was going to have to get a different phone. Read more

RISC-V Will Stop Hackers Dead From Getting Into Your Computer

The greatest hardware hacks of all time were simply the result of finding software keys in memory. The AACS encryption debacle — the 09 F9 key that allowed us to decrypt HD DVDs — was the result of encryption keys just sitting in main memory, where it could be read by any other program. DeCSS, the hack that gave us all access to DVDs was again the result of encryption keys sitting out in the open. Because encryption doesn’t work if your keys are just sitting out in the open, system designers have come up with ingenious solutions to prevent evil hackers form accessing these keys. One of the best solutions is the hardware enclave, a tiny bit of silicon that protects keys and other bits of information. Apple has an entire line of chips, Intel has hardware extensions, and all of these are black box solutions. They do work, but we have no idea if there are any vulnerabilities. If you can’t study it, it’s just an article of faith that these hardware enclaves will keep working. Now, there might be another option. RISC-V researchers are busy creating an Open Source hardware enclave. This is an Open Source project to build secure hardware enclaves to store cryptographic keys and other secret information, and they’re doing it in a way that can be accessed and studied. Trust but verify, yes, and that’s why this is the most innovative hardware development in the last decade. Read more

ONAP Myths Debunked

The Linux Foundation’s Open Network Automation Platform (ONAP) is well into its third 6-month release (Casablanca came out in Dec ’18), and while the project has evolved since it’s first release, there is still some confusion about what it is and how it’s architected. This blogs takes a closer look at ONAP, under-the-hood, to clarify how it works. To start, it is important to consider what functionality ONAP includes. I call ONAP a MANO++, where ONAP includes the NFVO and VNFM layers as described by ETSI, but goes beyond by including service assurance/automation and a unified design tool. ONAP does not include the NFVI/VIM or the NFV cloud layer. In other words, ONAP doesn’t really care whether the NFV cloud is OpenStack, Kubernetes or Microsoft Azure. Nor does ONAP include VNFs. VNFs come from third-party companies or open source projects but have VNF guidelines and onboarding SDKs that ease the deployment. In other words, ONAP is a modular platform for complete Network Automation. Read more