Language Selection

English French German Italian Portuguese Spanish

ArcoLinux 19.07.11

Filed under
Reviews

Today we are looking at the latest snapshot of ArcoLinux 19.07.11. We are looking at the main, edition, the XFCE release. It is based on Arch Linux, Linux Kernel 5.2, XFCE 4.12 and it uses about 600MB of ram when idling.

When I look at ArcoLinux, I can see just how much the developer loves this project and how much work he is putting into it. AcroLinux is clearly one of the best looking, and working great.

Read more

Direct/video: ArcoLinux 19.07.11 Run Through

ArchBang changes back to Openbox

  • [ArchBang] Change back to Openbox

    Did quite a bit of thinking regarding using i3 with ArchBang and it was starting to be obvious that many new users would be put off by tiling. Openbox is a comfortable window manager, easy to use and familiar. Its XML configs can be a pain but nothing that can be dealt with easily…

    Have switched Alt-F3 bind for dmenu to Super+d. Feels more natural and easier to reach. Removed Super+{h,v,c} from conky bind list too, really not sure of anyone needs them or even uses them. Can of course add in other binds.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights

How to Check Which Debian Version are you Running

Wondering which Debian version are you running? This tutorial teaches you several ways to check Debian version in the terminal. Read more