Language Selection

English French German Italian Portuguese Spanish

GNOME and KDE

Filed under
KDE
GNOME
  • digiKam 5.0.0-beta3 is released

    digiKam team is proud to announce the release of digiKam Software Collection 5.0.0 beta3. This version is new stage to the long way to stabilize code of Qt5 port of next main digiKam release. See previous announcement about 5.0.0-beta2 release to know all details about code re-writing under progress.

  • GNOME Developer Experience hackfest: xdg-app + Debian

    Over the last few days I've been at the GNOME Developer Experience hackfest in Brussels, looking into xdg-app and how best to use it in Debian and Debian derivatives.

  • We are getting there...

    In the last two weeks, I worked on adding minimaps, enabling the different layouts for long routes and shorter routes and the refactoring of code. After discussion with design team, it was confirmed that minimaps were to be added for starting and finishing points only.

More in Tux Machines

Google, IBM and Microsoft

  • Five Common Chromebook Myths Debunked
    When Chromebooks first came out in 2011, they were basically just low-spec laptops that could access web apps – fine for students maybe, but not to be regarded as serious computers. While they’ve become more popular (the low cost, simplicity, and dependability appeal to businesses and education systems), as of 2018 Chromebooks still haven’t managed to become widely accepted as a Windows/Apple/Linux alternative. That may be about to change. The humble Chromebook has gotten a lot of upgrades, so let’s get ourselves up to speed on some things that just aren’t true anymore. [...] The 2011 Chrome OS was pretty bare-bones, but it’s gone to the opposite extreme since then. Not only is it steadily blurring the line between Chrome and Android, it can now install and run some Windows programs as well, at the same time as a Chrome and an Android app, if you like. And hey, while you’re at it, why not open a Linux app as well? You can already install Linux on a Chromebook if you want, but one of the next versions of Chrome OS is going to include a Linux virtual machine accessible right from your desktop (which is already possible, just not built-in and user-friendly). In sum, Chrome OS has gone from barely being an operating system to one that can run apps from four other OSes at the same time.
  • Like “IBM’s Work During the Holocaust”: Inside Microsoft, Growing Outrage Over a Contract with ICE
  • Ubuntu Podcast from the UK LoCo: S11E15 – Fifteen Minutes - Ubuntu Podcast
    ...Microsoft getting into hot water over their work with US Immigration and Customs Enforcement. Plus we round up the community news.

KDE on Android: CI, CD & SDK

I guess we all agree that one of the biggest stoppers to get a contribution out is the ability to get the system ready to start working on the contribution. Today I want to talk a bit about generating Android binaries from our machine. In the KDE Edu sprint we had the blatant realisation that it’s very frustrating to keep pushing the project while not being swift at delivering fresh packages of our applications in different systems. We looked into windows, flatpak, snap and, personally, I looked into Android once again. Nowadays, KDE developers develop the applications on their systems and then create the binaries on their systems as well. Usually it’s a team effort where possibly just one person in the team will be familiar with Android and have the development combo in place: Android SDK, Android NDK, Qt binaries and often several KDE Frameworks precompiled. Not fun and a fairly complex premise. Read more Also:

today's howtos

Linux Kernel and Security: LVM2, Containers, AMD

  • LVM2 Begins Work On Major Changes To Logical Volume Management
    LVM2 as the user-space tools for Logical Volume Management (LVM) on Linux is in the process of going through a big re-work.
  • Containers and Cloud Security
    The idea behind this blog post is to take a new look at how cloud security is measured and what its impact is on the various actors in the cloud ecosystem. From the measurement point of view, we look at the vertical stack: all code that is traversed to provide a service all the way from input web request to database update to output response potentially contains bugs; the bug density is variable for the different components but the more code you traverse the higher your chance of exposure to exploitable vulnerabilities. We’ll call this the Vertical Attack Profile (VAP) of the stack. However, even this axis is too narrow because the primary actors are the cloud tenant and the cloud service provider (CSP). In an IaaS cloud, part of the vertical profile belongs to the tenant (The guest kernel, guest OS and application) and part (the hypervisor and host OS) belong to the CSP. However, the CSP vertical has the additional problem that any exploit in this piece of the stack can be used to jump into either the host itself or any of the other tenant virtual machines running on the host. We’ll call this exploit causing a failure of containment the Horizontal Attack Profile (HAP). We should also note that any Horizontal Security failure is a potentially business destroying event for the CSP, so they care deeply about preventing them. Conversely any exploit occurring in the VAP owned by the Tenant can be seen by the CSP as a tenant only problem and one which the Tenant is responsible for locating and fixing. We correlate size of profile with attack risk, so the large the profile the greater the probability of being exploited.
  • Canonical Releases AMD Microcode Updates for All Ubuntu Users to Fix Spectre V2
    Canonical released a microcode update for all Ubuntu users with AMD processors to address the well-known Spectre security vulnerability. The Spectre microprocessor side-channel vulnerabilities were publicly disclosed earlier this year and discovered to affect billions of devices made in the past two decades. Unearthed by Jann Horn of Google Project Zero, the second variant (CVE-2017-5715) of the Spectre vulnerability is described as a branch target injection attack.