In this project post, we pause our ongoing “Python in the Homelab” series to focus on a hands-on rebuild of a personal desktop environment. The goal is to provide a detailed account of setting up a minimal, highly functional Linux system on a new laptop using Arch Linux, paired with the lightweight Fluxbox window manager. This post emphasizes practical steps, real-world troubleshooting, and configuration choices, offering a roadmap for readers who want a fast, efficient desktop without unnecessary bloat.

Unlike many tutorials that rely heavily on screenshots, this article takes a textual approach, highlighting terminal commands, configuration files, and workflow adjustments. By documenting both successes and issues encountered, readers gain insight into the challenges of building a lightweight system from scratch, as well as the iterative process required to get it working reliably.

We also explore the combination of Fluxbox with XFCE panel elements, illustrating a hybrid desktop setup that balances speed and usability. The focus is on achieving a clean interface, fast system boot, and functional panel applets such as the Whisker Menu, network management, clipboard tools, and power monitoring, all while maintaining a cohesive Solarized theme.

Finally, this post highlights lessons learned during the Arch installation, keyring updates, package management, and configuration migration from an older system. By pausing the homelab series, we provide readers a chance to see a full, practical example of system customization and workflow optimization, showing how careful planning and iterative adjustment lead to a highly personalized, efficient Linux desktop.

Goals of the Project

The primary objectives of this rebuild were:

1. Establish a lightweight desktop that boots faster and runs more efficiently than the previous Xubuntu setup.
2. Use Arch Linux as the base, emphasizing minimalism and control over installed packages.
3. Employ Fluxbox as the window manager for a clean, highly configurable interface.
4. Incorporate XFCE4-panel to provide familiar panel functionality and applets without adding unnecessary desktop overhead.
5. Migrate existing files from the old laptop, including fonts, themes, and Conky settings.
6. Implement a visually consistent Solarized theme across GTK, icons, and Conky.
7. Maintain a smooth startup experience, with Picom for window compositing and Conky for system monitoring.

The guiding idea behind the project was straightforward: build only what is needed, keep the system fast, and preserve the tools that support daily workflow.

Tip: Before customizing the appearance of a new Linux installation, make sure the command-line environment and core utilities are complete and working.

Arch Linux Installation: Challenges and Considerations

Arch Linux is fundamentally different from Ubuntu, Xubuntu, and most traditional desktop distributions. Its rolling-release model and minimal install philosophy require the user to manually select packages, enable services, and troubleshoot problems that other distributions handle automatically.

The result is a system that is lean, transparent, and extremely customizable, but it also requires patience during installation.

Many of the command-line utilities needed during installation are discussed in the earlier article on
Essential Linux Commands, which served as a useful checklist while validating the base system.

Using the Arch 2022 Build Environment

This laptop required the Arch 2022 build environment due to hardware compatibility. That meant starting with an older installation image and adjusting the system during installation.

Several issues appeared immediately:

• Repository structure had changed since the ISO was released.
• The Arch keyring required multiple updates before package installation worked reliably.
• Each keyring update required rerunning the pacstrap step.
• The community repository had been merged into extra, which initially caused pacman failures.

Once the repositories were corrected and the keyring fully updated, the installation proceeded normally.

To make sure the command-line environment was complete, I compared the Arch installation against a working Ubuntu system. Tools such as ssh, rsync, netstat, editors, and networking utilities were confirmed to be present.

Lesson learned: Arch installs only the essentials. If you expect a utility to exist, verify it or install it explicitly.

Package installation and upgrades relied heavily on the pacman workflow discussed in the earlier
Package Management article.

Desktop Environment Setup

Display Manager

For graphical login, LightDM with the Slick Greeter was selected.

It worked immediately and provided a simple login experience. The theming, however, was not exactly what I expected. Rather than spending time debugging cosmetic issues, I left it alone.

Sometimes with Arch the best decision is simple: if it works, move on to the next task.

Window Manager: Fluxbox

Fluxbox serves as the window manager for this system.

It is:

• Extremely lightweight
• Fast to launch applications
• Highly configurable

However, Fluxbox behaves differently from XFCE in several areas:

• Window snapping
• Workspace switching
• Menu navigation

These differences required some adjustment.

After a short time using the system, the workflow started to feel natural again. Windows open quickly, workspaces behave predictably, and the system overall feels noticeably faster.

Observation: Fluxbox can feel unusual if you come from XFCE, but once you adjust, the workflow becomes very efficient.

The system boot time is also significantly faster than the previous Xubuntu installation, which was one of the primary goals of the rebuild.

XFCE Panel Integration

While Fluxbox handles window management well, it does not provide a modern panel environment by default.

To solve this, XFCE4-panel was added.

This hybrid approach provides the speed of Fluxbox with the usability of XFCE panel components.

Applets Added

The following panel applets were installed:

• Whisker Menu – application launcher
• Network Manager Applet – wired and wireless networking
• Parcellite – clipboard manager
• Bluetooth Applet – device monitoring and pairing
• XFCE Power Manager – battery and power status

Networking tools configured through the panel build on the concepts described in
Mastering Network Tools, which explains many of the utilities running behind the scenes.

Panel Configuration

The panel was configured with:

• 24px height
• Reserved screen space to prevent windows overlapping
• User menu actions for shutdown, reboot, and logout

Key Idea: Fluxbox manages windows, while XFCE provides panel usability. Separating those responsibilities keeps the system lightweight.

Desktop Quirks and Small Issues

A few small problems appeared during configuration.

Guake Terminal Key

Guake normally opens with F12, but on this laptop the function key required Fn + F12.

Once that was discovered, the issue was solved quickly.

Browser Window Behavior

Firefox initially opened beneath the panel, while Chromium did not.

After testing window options and compositor behavior, the issue was resolved using:

own_window_type = 'normal'

along with Picom compositing.

File Migration and Configuration

Configuration files and personal resources were copied from the previous system using SFTP through Thunar.

Priority files included:

• .fonts
• .icons
• .themes
• configuration directories

These resources restored the familiar environment while allowing the new system to remain lightweight.

Command-line reference during migration relied frequently on the
Ultimate Linux Cheat Sheet, particularly for file management and SSH utilities.

Conky Configuration

Conky provides system monitoring directly on the desktop.

The configuration from the previous laptop was reused and adjusted.

Key changes included:

• Replacing the Ubuntu logo with the Arch logo
• Adjusting vertical placement to avoid the panel
• Enabling subtle transparency

Important settings included:

own_window = true
own_window_type = 'normal'
own_window_argb_visual = true
own_window_argb_value = 150

Conky starts automatically through a startup script:

/home/jordan/.conky/conky-startup.sh &

A short delay (sleep 5) can help ensure the panel and compositor start first.

Solarized Theme Implementation

The desktop theme uses the Solarized color palette for consistency.

Primary colors:

• Background: #002b36 (base03)
• Primary text: #839496 (base0)
• Accent: #cb4b16

GTK themes, icons, and Conky colors were adjusted to match this palette.

The result is a desktop that is clean, readable, and visually consistent without being distracting.

Pull Quote: A minimal desktop is most effective when visual elements stay out of the way of the workflow.

Lessons Learned

Several lessons came out of this rebuild.

Arch requires planning.
Minimal installations are powerful but require careful package selection.

Older install media introduces complications.
Keyring updates and repository changes may require repeating installation steps.

Hybrid desktops work well.
Fluxbox handles windows efficiently, while XFCE panel components provide usability.

Workflow adaptation matters.
Switching window managers always requires a short adjustment period.

Minimal systems feel faster.
Boot times and application launches improved noticeably compared to the previous system.

Summary

Rebuilding this laptop with Arch Linux, Fluxbox, and XFCE4-panel resulted in a desktop environment that is both fast and practical. By selecting only the components required for daily use, the system avoids unnecessary overhead while still providing a familiar interface through the XFCE panel.

The installation process highlighted several realities of Arch Linux. Repository changes, keyring updates, and installation retries are sometimes unavoidable, especially when using older installation environments. Working through those issues reinforces an important aspect of Arch: understanding how the system is assembled gives you more control over the final result.

The combination of Fluxbox and XFCE panel components turned out to be particularly effective. Fluxbox provides fast window management and minimal resource usage, while the panel restores many of the conveniences typically found in a full desktop environment. The result is a hybrid setup that remains lightweight without sacrificing usability.

Although this article pauses the ongoing Python in the Homelab series, the lessons from this rebuild are directly relevant to homelab work. A well-configured Linux workstation remains one of the most valuable tools for managing infrastructure, experimenting with software, and documenting technical projects.