- Openbox and Tint2 Desktop Environment Configuration
About a year ago, I chose Solus Budgie, Budgie being the desktop environment, as a Linux distribution (distro) candidate for a mid-2009 MacBook Pro for my wife’s use. I ran Solus Budgie under VirtualBox on my two computers to learn how to use it so that I could provide tech support when my wife had questions.
I grew to really admire the fact that Solus appears to be a safe rolling release Linux distro. A rolling release Linux distro means that, unless an update or user error borks something, you should never have to install the distro again. I also admired the Solus Software Center app which allows you to easily locate and install software.
I’ve been a fan of the Openbox window manager and Tint2 panel as a Linux desktop environment since I began using CrunchBang Linux and later BunsenLabs. I liked Solus so much that I began desiring to add it as one of my daily drivers; Debian Stable and Debian Unstable being my other daily drivers. I began researching the possibility of running Solus using Openbox and Tint2. After some research of the Solus repositories (repos), I determined that I might be able to pull off running Solus with Openbox and Tint2.
I initially experimented running Solus with Openbox and Tint2 in one of my Solus installs under VirtualBox. I was able to get far enough along that I decided to take the plunge and install Solus as one of my daily drivers on my desktop computer. After a few weeks of experimenting and problem solving, I now have a very nice workable Openbox and Tint2 desktop environment running on Solus. In this blog post, I will share with you how I was able to setup an Openbox and Tint2 desktop environment under Solus Budgie v3.9999. With some variation, the same procedures should also work for the same version of Solus Mate and Solus Gnome.
Solus Budgie Installation
The first thing you need to do is download the Solus Budgie ISO file and install it on a thumb drive. I’m not going to cover how to install the ISO on a thumb drive or the installation process. If you would like more info about installing Solus Budgie, the Installation page of the Solus Help Center might be helpful.
I will point out an issue if you select a keyboard layout other than QWERTY (the default) during installation. I use the Dvorak keyboard layout and even though I’ve selected the layout during installation, the keyboard layout doesn’t work during installation or when logging in. If you opt to choose a keyboard layout other than QWERTY, then use a simple password like 123456 when setting up your user account during installation. I’ll address how to rectify the keyboard layout during login, as well as how to change your password, later in the tutorial.
Once you’ve installed Solus Budgie, the login screen should look something like the following, although the wallpaper will be different:
Note how the login area looks because after installing Openbox and Tint2, it will change in appearance. I’ll point out the change later in the tutorial.
If you don’t have a Broadcom wireless card/chip or if your Broadcom wireless card/chip is working, feel free to skip ahead.
In my past experiences of installing Solus Budgie, Broadcom wireless cards/chips weren’t recognized during installation. Therefore, if you have a Broadcom wireless chip/card, you may need to temporarily use an ethernet cable for Internet connectivity after installing Solus Budgie.
If your Broadcom wireless card isn’t working, first you need to install the appropriate driver. You can use the Solus Driver Management app (aka DoFlicky), Hardware Drivers from the Solus Budgie menu, which should present and enable you to install the appropriate driver, or you can use eopkg.
If you choose to use eopkg, drop to the command line (Terminal from the Solus Budge menu) and enter:
For the current Linux kernel…
For the legacy/stable Linux kernel…
To determine what kernel you’re using, drop to the command line and enter:
The S option in the above command is uppercased. If the value for Kernel is greater than 4.9.x, you’re using a current kernel.
After you’ve installed the Broadcom driver, drop to the command line and enter the following two commands:
Now reboot your computer. After entering the appropriate credentials for your router, you should have WiFi connectivity. Now you can put away the ethernet cable.
Once you have Solus Budgie installed, you should perform a system upgrade. I highly recommend using the eopkg package manager via the command line (Terminal from the Solus Budgie menu) instead of using the Solus Software Center app when performing the intial system upgrade. From the command line, issue the following command:
If extra packages need to be installed, you will be prompted and should answer yes to allow the system upgrade to continue.
Openbox and Tint2 Desktop Environment Installation
Now it’s time to add the necessary packages to create an Openbox and Tint2 desktop environment. Following are the packages that need to be installed:
arandr (screen layout editor), catfish (file search GUI), compton (window compositing), compton-conf (optional; GUI configuration for compton), feh (image viewer, used to set wallpaper), gtkhash (used to verify file hashes), i3lock (used to lock the user session), lxappearance (used to change/set appearance options), obconf (Openbox Configuration Manager) , obmenu (Openbox GUI menu editor), openbox (window manager), pavucontrol (PulseAudio Volume Control), polkit-gnome (super user authorization functionality), tint2 (panel)
You can install each package one at a time or install all at once by separating each package name with a space in the eopkg install command:
For those using a touchpad, Solus uses libinput by default and it works reasonably well with the proper configuration file (explained later in the tutorial). However, I use two different Logitech touchpads and I’ve found that the touchpads aren’t as responsive when using libinput. I opted to install the following two packages that provide touchpad configuration and functionality that work better in my opinion: xorg-driver-input-evdev, xorg-driver-input-synaptics.
Openbox and Tint2 Desktop Environment Configuration
At this point, you could reboot the computer and begin using the Openbox and Tint2 desktop environment. However, doing so will present you with nothing but a black screen, which might be a bit disconcerting. So, you’ll need to create folders and add/create configuration files so that things will be more user friendly when you first use the Openbox and Tint2 desktop environment.
Download the required configuration files here. You should also download and decompress the GPG signature for the compressed configuration files and verify it to insure that it hasn’t been tampered with. Verification should be performed prior to uncompressing the configuration files. You’ll need to use Kleopatra, in the Solus repos, or a similar app, and the Shared Bits public key to verify the file.
Under the /home/username/.config folder, create a folder named openbox. Copy the following files to the /home/username/.config/openbox folder:
autostart, menu.xml, rc.xml
The Openbox autostart file contains commands to start programs upon login. You’ll need to edit the autostart file and uncomment one of two lines to start compton on bootup. Make sure to save the file after making the change.
The menu.xml file contains the entries for the Openbox menu, accessible by right-clicking on the desktop or in the Tint2 panel, or by simultaneously pressing the Windows and Space keys.
The Openbox rc.xml file contains desktop settings and keybindings. I will provide a list of commonly used keybindings later in the tutorial. The desktop setting entries are usually modified using the Openbox Configuration Manager (obconf).
Next, create a folder named tint2 under the /home/username/.config folder. Copy the tint2rc file to the /home/username/.config/tint2 folder.
Copy the compton.conf file to the /home/username/.config folder.
If you are using the QWERTY keyboard layout (the default) under Solus Budgie, feel free to skip ahead.
If you chose to use a keyboard layout other than QWERTY during the Solus Budgie installation, the layout will not be available in the Openbox and Tint2 desktop environment. Edit the keyboard file and modify for your preferred layout. To get a list of keyboard layout names, drop to the command line and enter:
The first screen of output should look similar to the following:
Use the spacebar to advance screens, CTRL-C to quit. To search for a specific keyboard layout name:
For example, to search for Dvorak keyboard layout names or keymaps:
To see your current keyboard layout or keymap info:
Save your changes. Then as super user, copy the keyboard file to /etc/default. If your current keyboard layout doesn’t work in the login screen, the keyboard file will fix that issue as well.
If you chose a keyboard layout other than QWERTY during installation and used a simple password when setting up your account, you can now change your password to something stronger. From the command line, enter the following and respond to the prompts:
Note: I believe something has changed in Solus Budgie since the 4.00 release. Sometimes system upgrades cause the keyboard layout to revert back to QWERTY. Currently, the only method I have found to get the preferred keyboard layout back is to reboot the computer.
If you use a touchpad and are happy with libinput (default under Solus Budgie v3.9999), then as super user copy the 20-touchpad.conf file to the /etc/X11/xorg.conf.d folder. If you opted to install xorg-driver-input-evdev and xorg-driver-input-synaptics, then as super user copy the 50-synaptics.conf file to the /etc/X11/xorg.conf.d folder.
Now you’re ready to reboot. Are you excited? You should be.
Login Desktop Selector
Earlier in the tutorial, I asked you to pay attention to the login area because it would change after installing Openbox and Tint2. When you reboot your computer, a bird will appear in the login area, representing the Budgie desktop. If you look closely, you should be able to see that the bird is a desktop selector switch. When you click to the right of the desktop selector switch, you get a list of installed desktop environments. Click to the right of the desktop selector switch, select openbox from the list, and then login.
If you would like to have a wallpaper for your desktop, use Nautilus (Tools – File Manager in the Openbox menu) and navigate to the /usr/share/backgrounds folder or a folder containing an image you wish to use. Look through the folder(s), right-click on a desired image to use as a wallpaper, and select Open with feh. In feh, right-click on the image and select File-Background-Set Scaled/Set-Filled from the menu.
If you’d like to change the window decorations, icons, pointer, etc. select Settings – User Interface Settings from the Openbox menu and make the desired changes.
To change the login screen background image, start gnome-terminal and enter the following:
Next, open gedit as superuser [gedit (root) under the openbox menu category Tools-Editors] and enter the following lines:
Make sure to enter a line feed or carriage return (press the RETURN key) at the end of the last line. Save the file as /etc/lightdm/slick-greeter.conf. The selected image should be used as the login screen background image on the next reboot.
A big thank you goes out to users Lorien and yursan9 in the Solus forums for the login screen background image tip.
Commonly Used Keybindings
Take a look at the ~/.config/openbox/rc.xml file for a more extensive list. The file should be readable and editable in any text editor. Search for <keyboard> to find the start of the keybindings.
- Alt + Tab: produces a list of programs running on the current desktop. Release and press the Tab key to move the selector to the desired program to switch to.
- Alt + F2: Budgie Run Dialog (click in the box to enter a command/program name)
- Windows + F#: desktop switcher; e.g. F1 for desktop 1, F2 for desktop 2, etc.
- Windows + Spacebar: Openbox menu
- Windows + T: Gnome Terminal
- Windows + Tab: Brings up a list of all desktops and the programs running under each. The list can be traversed, using the up and down arrow keys, to switch to a desired program.
Issues/Missing in Action
The Settings app (gnome-control-center) that comes with Solus Budgie doesn’t work under Openbox and Tint2. You can run Settings, but you will not see much or be able to navigate within the app. However, since the Settings app is geared for the Budgie desktop, I’m not sure if any settings would work or work well under Openbox and Tint2.
There is no audio volume control applet for the Tint2 panel. On Debian, I use PNMixer, but that isn’t available in the Solus repos and I wasn’t able to locate anything familiar to me in the Solus repos that could be used as an audio volume control applet. My future plans are to attempt to compile PNMixer for use on Solus.
I currently use PulseAudio Volume Control (pavucontrol) to control audio volume. Click the third tab, Output Devices, click on the Speakers volume slider selector, and use the left and right arrow keys on your keyboard to control volume; left arrow decreases, right arrow increases. I leave PulseAudio Volume Control open and minimized so that I have ready access to change the volume; kind of kludgy, but it works.
There is no power management app. As of this blog post, I’m unaware of an existing text-based configuration file under Solus Budgie that might be usable for changing/setting power management options. Since there is no power management option, a period of inactivity will result in screen blanking.
On Debian, I use xfce4-power-manager, but that isn’t available in the Solus repos. My future plans are to attempt to compile xfce4-power-manager for use on Solus, unless I find something in the Solus repos between now and then.
The Budgie Run Dialog (ALT-F2) does not have focus when you run it. You must click in the box to enter a command or program name.
That’s it! You’re now running one of the leanest, meanest desktop environments in the OS world. If you’re a fan of minimalistic desktop environments, I think you’ll grow to love the combination of Openbox and Tint2. Enjoy!
I’d like to thank Philip Newborough, the sole developer and creator of CrunchBang Linux (#!), the CrunchBang Linux community members who continued CrunchBang Linux as BunsenLabs, and the many members of the forums of both distros. This tutorial would not have happened without you.
A thank you also goes out to the Solus developers for creating a really nice rolling release Linux distro and for providing Openbox and Tint2 in the repos.
To user pvsage who was a long time moderator in the CrunchBang Linux forums and a moderator for some time in the BunsenLabs forums, wherever you are, know that you are thought of and know that I and others hope you are doing okay.
Also check out a similar series of posts on running Openbox and Tint2 under Debian GNU/Linux:
Post header image courtesy of awpolop in the old Solus forums.
Updated on 2020-01-14