GNOME Security Internship - Update 5

This project started with a simple on/off switch in control center that entirely enabled or disabled the USB protection. A respectively so called always on and always off. Later on we introduced a smarter protection level that was active only when the user session was locked. While an always on protection seemed a good idea on paper it turned out that the advantages compared to the lock screen protection were very slim. When the screen is locked both protections have the same behaviour. They only differentiate when the user session is unlocked.

Pick a clock, any clock.

After listening to the latest episode of Emmanuel’s podcast on the History of GNOME, nostalgia got the better of me, and I decided to dig out the GNOME 1.4 usability study that we ran at Sun Microsystems in March 2001, and make it available online again.

Who wrote librsvg?

The shitty thing about a gradual rewrite is that a few people end up "owning" all the lines of source code. Hopefully this post is a little acknowledgment of the people that made librsvg possible. The charts are made with the incredible tool git-of-theseus — thanks to @norwin@mastodon.art for digging it up! Its README also points to a Hercules plotter with awesome graphs. You know, for if you needed something to keep your computer busy during the weekend.

Lumina Desktop will be removed from my -current repository

The Lumina Desktop is part of the TrueOS project, a FreeBSD variant. I packaged version 1.4.0.p1 for Slackware and it is part of the Plasma5 variant of my Slackware Live Edition. I noticed a while ago that Lumina would no longer start but it was low on my priority list to try and fix it. Today I found the time to look into this, but a recompilation against the latest Qt5 and other libraries, altough error-free, would not make the Lumina Desktop start successfully: it will start to load, but then you’ll hear a beep and you’re dumped at the command prompt or at the graphical login screen without evidence of what happened.

Valentine present for Slackers

Today is Valentine’s Day. A moment to give some extra attention to people that are dear to you. In my case, that’s everyone who loves, uses, supports, advocates or develops Slackware Linux. For all of you, I uploaded “KDE-5_19.02” to the ‘ktown‘ repository. There’s some updates in there that might interest you, see below. If you do not (want to) run or install Slackware-current, I will make sure that a new ISO of the Slackware Live Plasma5 Edition will be available around the weekend. That way, you can safely try it out without having to touch your hard drive. As always, these packages are meant to be installed on a Slackware-current which has had its KDE4 removed first. These packages will not work on Slackware 14.2.

Networking Tool Comics!

How to Play Playstation 2 Games on Linux with PCSX2

How to Install GNU Emacs 26.1 in Ubuntu 18.04, 16.04, 18.10

Create multiple subfolders in one command.

How to Create Bootable Ubuntu 18.04 USB Stick on Linux

Everyday Regular Expressions

Deploying HA MongoDB on OpenShift using Portworx

Debugging experience in Debian

Proposed Change to EPEL Policies: Minor Release Based Composes

The change moves EPEL composes to biannual based composes and adds an updates tree for consumers. Package trees will have a naming structure similar to Fedora release names, and will be regularly archived off to /pub/archives after the next minor release. Package lifetimes will be similarly affected with the expected minimum 'support' lifetime of any package to be that of a minor release.

Fedora Community Blog: FPgM report: 2019-07

Here’s your report of what has happened in Fedora Program Management this week. I’ve set up weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.

Fedora 30 Might Enable DNF's "Best" Mode By Default

Under a late change proposal for Fedora 30, the DNF package manager's "best" mode might be enabled by default. The --best option for DNF always tries to upgrade to the highest version available even if dependencies cannot be satisfied. While it may make sense for DNF to always try going for the latest and greatest package version which is in line with most other Linux package managers, the current behavior aims for the latest version where all package dependencies can be satisfied. If a newer package version is available but with unmet dependencies, the current default DNF behavior will silently ignore that newer version.

Bodhi 3.13.0 released