Language Selection

English French German Italian Portuguese Spanish

Ubuntu

Ubuntu 16.04.5 LTS, Lubuntu 16.04.5, and UBports' Ubuntu Touch on 16.04.x

Filed under
Ubuntu
  • Ubuntu 16.04.5 LTS Released on Heels of Ubuntu 18.04 LTS, Bundles All Past Stable Release Updates

    A few days ago we covered the release of Ubuntu 18.04 LTS, and also the NCSC’s guidelines on Ubuntu 18.04 security, but there’s more news yet from the Ubuntu team – they just released Ubuntu 16.04.5 Xenial Xerus LTS (Long Term Support) for folks who will not upgrade to Ubuntu 18.04 LTS.

    This latest update to Ubuntu 16.04 has a new hardware enablement stack intended to work with the latest hardware out-of-the-box. Support for this is offered on all architectures except 32-bit powerpc, and it is installed by default when using the desktop images as an installation media. Ubuntu Server will default to installing the GA kernel, but users can optionally choose to install the HWE kernel instead.

  • Ubuntu 16.04.5 LTS Released, Available to Download Now

    Download Ubuntu 16.04.5 LTS, the fifth (and final) point release of Ubuntu 16.04 LTS. It features Linux kernel 4.15, Xorg updates, and various bug fixes.

  • Ubuntu 16.04.5 LTS released

    The Ubuntu team is pleased to announce the release of Ubuntu 16.04.5 LTS (Long-Term Support) for its Desktop, Server, and Cloud products, as well as other flavours of Ubuntu with long-term support.

    Like previous LTS series’, 16.04.5 includes hardware enablement stacks for use on newer hardware. This support is offered on all architectures except for 32-bit powerpc, and is installed by default when using one of the desktop images. Ubuntu Server defaults to installing the GA kernel, however you may select the HWE kernel from the installer bootloader.

    As usual, this point release includes many updates, and updated installation media has been provided so that fewer updates will need to be downloaded after installation. These include security updates and corrections for other high-impact bugs, with a focus on maintaining stability and compatibility with Ubuntu 16.04 LTS.

  • Lubuntu 16.04.5 has been released!

    Thanks to all the hard work from our contributors, we are pleased to announce that Lubuntu 16.04.5 LTS has been released!

  • UBports' Ubuntu Touch Unlikely To Move To Ubuntu 18.04 Anytime Soon

    Given that it was only earlier this summer when UBports' Ubuntu Touch OTA-4 upgraded to an Ubuntu 16.04 LTS base, you might be wondering when they intend to transition to Ubuntu 18.04 LTS... But don't hold your breath.

    During the latest Ubuntu Touch Q&A, the matter came up of if/when they will transition from Ubuntu 16.04 to Ubuntu 18.04 as the newest Long Term Support release. But long story short is they have no immediate plans to do so.

    The resources of the community-driven UBports is limited as is and the migration to Ubuntu 18.04 would require systemd, among other changes, as well as 18.04 using newer versions of Mir, Unity 8, and libhybris that would conflict with the current UBports work.

Proprietary: ​Opera as Snap on GNU/Linux, Chrome 69 Beta

Filed under
Software
Ubuntu
  • Opera launches as a Snap for Linux users

    Opera and Canonical today announce that Opera, the popular web browser, is now available as a Snap in the Snap Store. Opera is the latest notable addition to the Snap Store providing ever more choice to Linux users via an easy to install, always up to date application direct from the software vendor.

    Opera, founded in 1995 in Oslo has been delivering browsers and AI-driven content delivery products to 322 million users worldwide across a range of devices and operating systems. It is responsible for now standardised browser features such as tabs or speed dial. Currently, it is the browser of choice for more demanding users who seek features such as a built-in VPN, ad blocker or a separate messengers sidebar.

  • ​Opera is available in a Snap on Linux

    They've done this by packing Opera into a Snap in the Snap Store. The Opera snap is supported on Debian, Elementary, Fedora, Linux Mint, Manjaro, OpenSUSE, Ubuntu, and other Linux distributions.

    Snaps are containerised software packages. They're designed to work securely within any Linux environment across desktop, the cloud, and IoT devices. Thousands of snaps have been launched since 2016. Users like them because they come with automatic updates and roll-back features.

    Snaps also are a bit more secure than most Linux apps. They make it easier for developers to roll out their programs. When your program in encased in a Snap, you don't need to worry about the distribution's native packaging or whether the desktop distro includes a vital library your application needs.

  • Opera Web Browser Is Now Available as a Snap on Ubuntu, Other Linux Distros

    Canonical and Opera Software informs Softpedia today about the availability of the Chromium-based Opera web browser as a Snap package in the Snap Store for Ubuntu and supported Linux-based operating systems.

    Used by more than 322 million users worldwide on a wide range of devices and computer operating systems, including GNU/Linux, macOS, and Microsoft Windows, Opera is a very popular web browser based on the latest technologies from the open-source Chromium project. On Linux platforms, users can install Opera as DEB and RPM packages.

  • Opera Browser is Now Available in the Ubuntu Snap Store

    It just got a whole lot easier to install the Opera web browser on Ubuntu and other Linux distros. Canonical has announced that the well-known web browser is now available as a Snap app in the Ubuntu Snap store.

  • Chrome 69 Beta: CSS tricks, and more

    Unless otherwise noted, changes described below apply to the newest Chrome Beta channel release for Android, Chrome OS, Linux, macOS, and Windows. View a complete list of the features in Chrome 69 on ChromeStatus.com. Chrome 69 is beta as of August 2.

  • Chrome 69 Beta Released With AV1 Decode & Various CSS Additions

    Google has rolled out the Chrome 69 beta web-browser update today for Linux, Android, and other supported platforms.

    Chrome 69 Beta is quite exciting in that it introduces initial support for AV1 video decoding support -- albeit still in very early form but now possible thanks to AV1 v1.0 being firmed up. There are also a number of CSS styling enhancements with Chrome 69 Beta including support for conic gradients, new margin/padding/border properties, scroll snap positions, display cutouts, and more.

How to Install and Configure Sound Themes in Ubuntu

Filed under
Ubuntu

This beginner’s guide will explain how you can install sound themes in Ubuntu.

If you like to give your desktop different look and feel via various themes, icon themes, then why not sound also. There are plenty of cool sound themes available in Ubuntu covering lots of events. This gives a feel of life in your Ubuntu desktop experience, rather than a ‘silent’ usage. Here’s how you can install sound theme in Ubuntu.

We have chosen “Smooth” sound theme containing 58 system events.

Read more

Ubuntu 16.04.5 LTS (Xenial Xerus) Released as Last in the Series, Download Now

Filed under
Ubuntu

Every LTS (Long Term Support) version of the Ubuntu Linux operating system is supported by Canonical with security and software updates for five years on the Ubuntu Desktop, Server, and Cloud images, and they received a total of five point releases every six months or so.

Dubbed Xenial Xerus, Ubuntu 16.04 LTS was released on April 21, 2016, with the Unity desktop environment, and it's supported until April 2021. The Ubuntu 16.04.5 LTS point release is the last in the series and like all the previous point releases, it represents an up-to-date installation medium for those who want to install a fresh Ubuntu 16.04 LTS system.

Read more

Also: Ubuntu 16.04.5 LTS Released For Those Not Yet Upgrading To Ubuntu 18.04

Ubuntu: uCaresystem, Server, and National Cyber Security Centre (NCSC)

Filed under
Ubuntu
  • How to keep your Ubuntu Linux systems updated with uCaresystem

    If you're like me, you prefer to keep your Linux systems as up to date as possible. After all, vulnerabilities are patched, new features are added, and a server or desktop can be made to run more smoothly and securely by keeping it as "in the now" as possible. To that end, most users will open up a terminal window and run the tried-and-true sudo apt-get update && sudo apt-get upgrade command to catch anything available for their system.

    The thing is, those two commands either may not catch everything or they leave behind outdated files that can lead to problems down the road. Of course, you could add to your list of commands the likes of sudo apt-get autoremove and apt-get clean. Wouldn't it be nice if there were a single tool to take care of all that? Oh wait, there is! That tool is called uCareSystem. Let's install and use this one-stop-shop updater.

  • Ubuntu Server development summary – 31 July 2018

    The purpose of this communication is to provide a status update and highlights for any interesting subjects from the Ubuntu Server Team. If you would like to reach the server team, you can find us at the #ubuntu-server channel on Freenode. Alternatively, you can sign up and use the Ubuntu Server Team mailing list.

  • UK cyber security boffins dispense Ubuntu 18.04 wisdom

    The UK’s National Cyber Security Centre (NCSC) has dispensed advice aimed at securing Ubuntu installs and followed it up with help for Dixons customers.

    The NCSC, part of the UK’s Government Communications Headquarters (GCHQ) exists to make the UK a safer place to do business online and, in an unusual step for a Government agency, does a pretty good job of dispensing sensible security advice.

    Dixons Carphone customers got the treatment yesterday, following the admission that, er, maybe a bit more than 1.2 million users had actually had their privates exposed in a data breach. More like 10 million records. GCHQ's infosec crew suggested Dixons users shouldn't fill in their log-in info via that link on that unsolicited email, hmm?

    Last week, however, it was Ubuntu 18.04 LTS upon which the agency turned its gimlet gaze. The security wonks first stated the obvious – route data over a secure VPN to avoid prying eyes, stop users installing whatever they want and for goodness sake, cut down on the admin rights.

New Login Screen of Ubuntu 18.10 (Cosmic Cuttlefish)

Filed under
Ubuntu

A quick look at the upcoming Ubuntu 18.10 login screen via Yaru theme.

Ubuntu 18.10 (Cosmic Cuttlefish), the next major release of Ubuntu operating system which is currently in development. Among all the features, enhancements of Ubuntu 18.10, the main attractive feature is the look-n-feel. With 18.10 release, Ubuntu is bringing change to its default theme with a new theme called ‘Communitheme’ which is recently renamed as Yaru.

Read more

The best way to update and install apps on Ubuntu

Filed under
Ubuntu

Ubuntu is a great Linux distribution that is soon to become even better. Already it's stable, secure, and user-friendly, so what's about to change? Recently I received an interesting question about Ubuntu. The question was about the best way to update and install apps on Ubuntu. That's where one major improvement is about to happen.

The thing that needs to be considered, for Ubuntu, is that they are migrating over to GNOME in 17.10, which means the now-defunct Ubuntu Software Center is officially switching to GNOME Software. This is a good thing on so many levels. First off, the Ubuntu Software Center has been broken for a long time. Also, with the old system, you had to install software from one tool and upgrade software from another. Now, thanks to the new GNOME Software tool, everything happens in one happy location.

Read more

Xubuntu Development Update August 2018

Filed under
GNU
Linux
Ubuntu

This is the final point release for Xubuntu 16.04 “Xenial Xerus”. As Xubuntu has a 3-year support cycle, this release will be supported until April 2019. There have not been any major changes from the Xubuntu team for this point release, but there have been a number of other improvements and security updates for other components.

16.04.5 is expected to be released tomorrow, August 2, 2018. If you have a few moments, feel free to do some testing and make sure everything is working as well as we think it is!

Read more

Also: Snapcraft Build Environments

Ubuntu 16.04.5 LTS Release Candidate Ready for Testing Ahead of August 2 Release

Filed under
Ubuntu

Canonical's Lukasz Zemczak put out a call for testing today for the upcoming Ubuntu 16.04.5 LTS point release of the Ubuntu 16.04 LTS (Xenial Xerus) operating system series.

Release Candidate (RC) images of the Ubuntu 16.04.5 LTS point release, which is the fifth and also the last for the long-term supported Ubuntu 16.04 LTS (Xenial Xerus) operating system, are now ready for public testing. The Ubuntu community is urged to download and test drive the new RC images in case some unknown issues arise.

Read more

Original: First set of 16.04.5 RC images ready for testing

Here's the New Login Screen of Ubuntu 18.10 (Cosmic Cuttlefish) with Yaru Theme

Filed under
Ubuntu

One of the most attractive things about the forthcoming Ubuntu 18.10 operating system, due for release later this fall on October 18, 2018, is its new look and feel, which is provided by the so-called Communitheme that was recently renamed as Yaru, a system-wide theme for Ubuntu Desktop.

As part of this community initiative, Ubuntu 18.10 will get a brand-new look and feel that will make the popular computer operating system more modern, more accessible, and more attractive. And, today we finally have a first look at the Yaru theme on the current Ubuntu 18.10 (Cosmic Cuttlefish) development release.

Read more

Syndicate content

More in Tux Machines

Red Hat's "DevOps" Hype Again and Analysis of last Night's Financial Results

OSS Leftovers

  • Deutsche Telekom and Aricent Create Open Source Edge Software Framework
    Deutsche Telekom and Aricent today announced the creation of an Open Source, Low Latency Edge Compute Platform available to operators, to enable them to develop and launch 5G mobile applications and services faster. The cost-effective Edge platform is built for software-defined data centers (SDDC) and is decentralized, to accelerate the deployment of ultra-low latency applications. The joint solution will include a software framework with key capabilities for developers, delivered as a platform-as-a-service (PaaS) and will incorporate cloud-native Multi-access edge computing (MEC) technologies.
  • A Deeper Look at Sigma Prime's Lighthouse: An Open-Source Ethereum 2.0 Client
  • Notable moments in Firefox for Android UA string history
  • Dweb: Creating Decentralized Organizations with Aragon
    With Aragon, developers can create new apps, such as voting mechanisms, that use smart contracts to leverage decentralized governance and allow peers to control resources like funds, membership, and code repos. Aragon is built on Ethereum, which is a blockchain for smart contracts. Smart contracts are software that is executed in a trust-less and transparent way, without having to rely on a third-party server or any single point of failure. Aragon is at the intersection of social, app platform, and blockchain.
  • LLVM 7.0.0 released
  • Parabola GNU/Linux-libre: Boot problems with Linux-libre 4.18 on older CPUs
    Due to a known bug in upstream Linux 4.18, users with older multi-core x86 CPUs (Core 2 Duo and earlier?) may not correctly boot up with linux-libre 4.18 when using the default clocksource.
  • Visual Schematic Diffs in KiCAD Help Find Changes
    In the high(er)-end world of EDA tools like OrCAD and Altium there is a tight integration between the version control system and the design tools, with the VCS is sold as a product to improve the design workflow. But KiCAD doesn’t try to force a version control system on the user so it doesn’t really make sense to bake VCS related tools in directly. You can manage changes in KiCAD projects with git but as [jean-noël] notes reading Git’s textual description of changed X/Y coordinates and paths to library files is much more useful for a computer than for a human. It basically sucks to use. What you really need is a diff tool that can show the user what changed between two versions instead of describe it. And that’s what plotgitsch provides.

LWN's Latest (Today Outside Paywall) Articles About the Kernel, Linux

  • Toward better handling of hardware vulnerabilities
    From the kernel development community's point of view, hardware vulnerabilities are not much different from the software variety: either way, there is a bug that must be fixed in software. But hardware vendors tend to take a different view of things. This divergence has been reflected in the response to vulnerabilities like Meltdown and Spectre which was seen by many as being severely mismanaged. A recent discussion on the Kernel Summit discussion list has shed some more light on how things went wrong, and what the development community would like to see happen when the next hardware vulnerability comes around. The definitive story of the response to Meltdown and Spectre has not yet been written, but a fair amount of information has shown up in bits and pieces. Intel was first notified of the problem in July 2017, but didn't get around to telling anybody in the the Linux community about it until the end of October. When that disclosure happened, Intel did not allow the community to work together to fix it; instead each distributor (or other vendor) was mostly left on its own and not allowed to talk to the others. Only at the end of December, right before the disclosure (and the year-end holidays), were members of the community allowed to talk to each other. The results of this approach were many, and few were good. The developers charged with responding to these problems were isolated and under heavy stress for two months; they still have not been adequately thanked for the effort they put in. Many important stakeholders, including distributions like Debian and the "tier-two" cloud providers, were not informed at all prior to the general disclosure and found themselves scrambling. Different distributors shipped different fixes, many of which had to be massively revised before entry into the mainline kernel. When the dust settled, there was a lot of anger left simmering in its wake.
  • Writing network flow dissectors in BPF
    Network packet headers contain a great deal of information, but the kernel often only needs a subset of that information to be able to perform filtering or associate any given packet with a flow. The piece of code that follows the different layers of packet encapsulation to find the important data is called a flow dissector. In current Linux kernels, the flow dissector is written in C. A patch set has been proposed recently to implement it in BPF with the clear goal of improving security, flexibility, and maybe even performance.
  • Coscheduling: simultaneous scheduling in control groups
    The kernel's CPU scheduler must, as its primary task, determine which process should be executing in each of a system's processors at any given time. Making an optimal decision involves juggling a number of factors, including the priority (and scheduling classes) of the runnable processes, NUMA locality, cache locality, latency minimization, control-group policies, power management, overall fairness, and more. One might think that throwing another variable into the mix — and a complex one at that — would not be something anybody would want to attempt. The recent coscheduling patch set from Jan Schönherr does exactly that, though, by introducing the concept of processes that should be run simultaneously. The core idea behind coscheduling is the marking of one or more control groups as containing processes that should be run together. If one process in a coscheduled group is running on a specific set of CPUs (more on that below), only processes from that group will be allowed to run on those CPUs. This rule holds even to the point of forcing some of the CPUs to go idle if the given control group lacks runnable processes, regardless of whether processes outside the group are runnable. Why might one want to do such a thing? Schönherr lists four motivations for this work, the first of which is virtualization. That may indeed be the primary motivation, given that Schönherr is posting from an Amazon address, and Amazon is rumored to be running a virtualized workload or two. A virtual machine usually contains multiple processes that interact with each other; these machines will run more efficiently (and with lower latencies) if those processes can run simultaneously. Coscheduling would ensure that all of a virtual machine's processes are run together, maximizing locality and minimizing the latencies of the interactions between them.
  • Machine learning and stable kernels
    There are ways to get fixes into the stable kernel trees, but they require humans to identify which patches should go there. Sasha Levin and Julia Lawall have taken a different approach: use machine learning to distinguish patches that fix bugs from others. That way, all bug-fix patches could potentially make their way into the stable kernels. Levin and Lawall gave a talk describing their work at the 2018 Open Source Summit North America in Vancouver, Canada. Levin began with a quick introduction to the stable tree and how patches get into it. When a developer fixes a bug in a patch they can add a "stable tag" to the commit or send a mail to the stable mailing list; Greg Kroah-Hartman will then pick up the fix, evaluate it, and add it to the stable tree. But that means that the stable tree is only getting the fixes that are pointed out to the stable maintainers. No one has time to check all of the commits to the kernel for bug fixes but, in an ideal world, all of the bug fixes would go into the stable kernels. Missing out on some fixes means that the stable trees will have more security vulnerabilities because the fixes often close those holes—even if the fixer doesn't realize it.
  • Trying to get STACKLEAK into the kernel
    The STACKLEAK kernel security feature has been in the works for quite some time now, but has not, as yet, made its way into the mainline. That is not for lack of trying, as Alexander Popov has posted 15 separate versions of the patch set since May 2017. He described STACKLEAK and its tortuous path toward the mainline in a talk [YouTube video] at the 2018 Linux Security Summit. STACKLEAK is "an awesome security feature" that was originally developed by The PaX Team as part of the PaX/grsecurity patches. The last public version of the patch set was released in April 2017 for the 4.9 kernel. Popov set himself on the goal of getting STACKLEAK into the kernel shortly after that; he thanked both his employer (Positive Technologies) and his family for giving him working and free time to push STACKLEAK. The first step was to extract STACKLEAK from the more than 200K lines of code in the grsecurity/PaX patch set. He then "carefully learned" about the patch and what it does "bit by bit". He followed the usual path: post the patch, get feedback, update the patch based on the feedback, and then post it again. He has posted 15 versions and "it is still in progress", he said.

PostgreSQL 11: something for everyone

PostgreSQL 11 had its third beta release on August 9; a fourth beta (or possibly a release candidate) is scheduled for mid-September. While the final release of the relational database-management system (currently slated for late September) will have something new for many users, its development cycle was notable for being a period when the community hit its stride in two strategic areas: partitioning and parallelism. Partitioning and parallelism are touchstones for major relational database systems. Proprietary database vendors manage to extract a premium from a minority of users by upselling features in these areas. While PostgreSQL has had some of these "high-tier" items for many years (e.g., CREATE INDEX CONCURRENTLY, advanced replication functionality), the upcoming release expands the number considerably. I may be biased as a PostgreSQL major contributor and committer, but it seems to me that the belief that community-run database system projects are not competitive with their proprietary cousins when it comes to scaling enterprise workloads has become just about untenable. Read more