Language Selection

English French German Italian Portuguese Spanish

today's leftovers

Filed under
Misc
  • Chromebook Users Will Soon Be Able to Install Debian Packages via the Files App

    Google continues to work on the Linux app support implementation for its Linux-based Chrome OS operating system for Chromebooks by adding initial support for installing Debian packages via the Files app.

    Linux app support in Chrome OS is here, but it's currently in beta testing as Google wants to make it ready for the masses in an upcoming stable Chrome OS release. Meanwhile, Google's Chrome OS team details in a recent Chromium Gerrit commit initial support for installing Linux packages in the .deb file format used by Debian-based operating systems directly from the Files app.

  • Phoronix Test Suite 8.2 Milestone 1 Released For Open-Source Benchmarking

    The first development snapshot of Phoronix Test Suite 8.2 is now available as what will be the next quarterly feature update to our open-source Linux / BSD / macOS / Windows automated benchmarking software and framework.

  • How To Install Plex Media Server on CentOS 7
  • How to Recover Files from Corrupted or Damaged ReiserFS File Systems? DiskInternals Has the Answer
  • DXVK 0.63 Released With Support For NVIDIA's Latest Driver

    For those planning to enjoy their favorite Direct3D 11 games under Wine this weekend and utilizing the DXVK D3D11-over-Vulkan layer for greater performance, DXVK 0.63 is now available.

    First up with DXVK 0.63 is compatibility with the newly-released NVIDIA 396.45 stable driver release due to Vulkan driver changes.

  • Northgard introduces the Clan of the Snake in a new DLC

    Thriving in the harsh northern lands in Northgard isn’t particularly easy and the new Snake Clan faction adds a few twists to the enjoyable Viking experience. An update that released alongside the DLC also adds several bells and whistles to all players for free.

  • Meg Ford: GUADEC 2018

    I was particularly interested in and disappointed by Michael Catanzaro's talk "Migrating from JHBuild to BuildStream". I appreciate all the time and effort the Release Team has put into maintaining and developing the build systems, so I'm including my experience here as an example, not as a criticism.
    Over time I've gotten used to JHBuild and become adept at searching for and fixing its sometimes bizarre error messages. A few months ago, after running into some modules that failed on JHBuild, I read the announcement about GNOME's modulesets moving to BuildStream. I spent a couple days removing JHBuild and rebuilding everything in BuildStream. Except I ran out of disk space. So I removed as much as I could and started over. Except then PulseAudio wouldn't work. Luckily I'd occasionally run into the same errors caused by an unavailable PulseAudio daemon when I was using JHBuild. I tried restarting the daemon, etc, and looked for info on the subject. In the end it turned out that PulseAudio wasn't available within the sandbox, so I scrapped BuildStream and went back to JHBuild.
    Going forward, I'm planning to move from JHBuild to using FlatPak, Builder, and GNOME's nightly runtime build. I'm happy that the community is providing solutions, and, while things are still in a confusing state, at least they are moving quickly in interesting and promising directions.

  • On Flatpak Nightlies

    As far as I know, it was not possible to run any nightly applications during this two week period, except developer applications like Builder that depend on org.gnome.Sdk instead of the normal org.gnome.Platform. If you used Epiphany Technology Preview and wanted a functioning web browser, you had to run arcane commands to revert to the last good runtime version.

    This multi-week response time is fairly typical for us. We need to improve our workflow somehow. It would be nice to be able to immediately revert to the last good build once a problem has been identified, for instance.

    Meanwhile, even when the runtime is working fine, some apps have been broken for months without anyone noticing or caring. Perhaps it’s time for a rethink on how we handle nightly apps. It seems likely that only a few apps, like Builder and Epiphany, are actually being regularly used. The release team has some hazy future plans to take over responsibility for the nightly apps (but we have to take over the runtimes first, since those are more important), and we’ll need to somehow avoid these issues when we do so. Having some form of notifications for failed builds would be a good first step.

  • TLS 1.3 Via GnuTLS Is Planned For Fedora 29

    The feature list for Fedora 29 continues growing and the latest is about shipping GnuTLS with TLS 1.3 support enabled.

    TLS 1.3 was approved by the Internet Engineering Task Force earlier this year as the newest version of this protocol for making secure web connections that is key to HTTPS. TLS 1.3 offers various security and performance improvements over TLS 1.2 as well as lower-latency, better handling of long-running sessions, etc.

  • Xubuntu 17.10 EOL

    On Thursday 19th July 2018, Xubuntu 17.10 goes End of Life (EOL). For more information please see the Ubuntu 17.10 EOL Notice.

  • Linux Mint developers planning big Cinnamon 4.0 improvements

    Linux Mint is one of the most popular Linux-based desktop operating systems for a reason -- it’s really good. By leveraging the excellent Ubuntu for its base, and offering a top-notch user experience, success is pretty much a guarantee.

    While the distribution primarily focuses on two desktop environments -- Mate and Cinnamon -- the latter is really the star of the show. Cinnamon is great because it uses a classic WIMP interface that users love, while also feeling modern. With Cinnamon 3.8, the Linux Mint Team focused on improving the DE's performance, and today, the team shares that it is continuing that mission with the upcoming 4.0. In particular, the team is focusing on Vsync.

More in Tux Machines

today's howtos

Get started with Roland, a random selection tool for the command line

There seems to be a mad rush at the beginning of every year to find ways to be more productive. New Year's resolutions, the itch to start the year off right, and of course, an "out with the old, in with the new" attitude all contribute to this. And the usual round of recommendations is heavily biased towards closed source and proprietary software. It doesn't have to be that way. Here's the seventh of my picks for 19 new (or new-to-you) open source tools to help you be more productive in 2019. Read more

Nginx vs Apache: Which Serves You Best in 2019?

For two decades Apache held sway over the web server market which is shrinking by the day. Not only has Nginx caught up with the oldest kid on the block, but it is currently the toast of many high traffic websites. Apache users might disagree here. That is why one should not jump to conclusions about which web server is better. The truth is that both form the core of complete web stacks (LAMP and LEMP), and the final choice boils down to individual needs. For instance, people running Drupal websites often call on Apache, whereas WordPress users seem to favor Nginx as much if not more. Accordingly, our goal is to help you understand your own requirements better rather than providing a one-size recommendation. Having said that, the following comparison between the two gives an accurate picture. Read more

Security: Updates, 'Smart' Things, Android Proprietary Software and Firefox Woes on Windows

  • Security updates for Friday
  • How Do You Handle Security in Your Smart Devices?
    Look around your daily life and that of your friends and family, and you’ll see that smart devices are beginning to take over our lives. But this also means an increase in a need for security, though not everyone realizes it, as discussed in a recent article on our IoT-related site. Are you aware of the need for security even when it’s IoT-related? How do you handle security in your smart devices?
  • A Vulnerability in ES File Explorer Exposes All of Your Files to Anyone on the Same Network
  • 2018 Roundup: Q1
    One of our major pain points over the years of dealing with injected DLLs has been that the vendor of the DLL is not always apparent to us. In general, our crash reports and telemetry pings only include the leaf name of the various DLLs on a user’s system. This is intentional on our part: we want to preserve user privacy. On the other hand, this severely limits our ability to determine which party is responsible for a particular DLL. One avenue for obtaining this information is to look at any digital signature that is embedded in the DLL. By examining the certificate that was used to sign the binary, we can extract the organization of the cert’s owner and include that with our crash reports and telemetry. In bug 1430857 I wrote a bunch of code that enables us to extract that information from signed binaries using the Windows Authenticode APIs. Originally, in that bug, all of that signature extraction work happened from within the browser itself, while it was running: It would gather the cert information on a background thread while the browser was running, and include those annotations in a subsequent crash dump, should such a thing occur.