Razor-qt is a relatively new desktop environment built atop Qt technologies. From the ground up, it is designed to be resource-friendly, so that it can run on old and new computers alike. It hasn’t gotten a lot of press, but I’ve been keeping track of its development since it was started.
The latest edition is Razor-qt 0.5.2. This article shows how to install it on Ubuntu 12.10 or any other edition of Ubuntu you might be running.
Because it is a relatively new project, do not be surprised at the occasional application-crash or some other error that signals instability in the system.
Installing Razor-qt in Ubuntu involves adding the repository, updating the applications database, and finally, installing the Razor-qt packages.
1. Add Razor-qt Repository: To add the Razor-qt repository to your software sources, type:
sudo add-apt-repository ppa:razor-qt
2. Update Applications Database: To update the applications database, type: sudo apt-get update
3. Install Razor-qt: You can install it from the command line or via the Software Center, if you prefer working with a graphical interface. From the command line (first launch a terminal), type: sudo apt-get install razorqt
To install it via a graphical interface, start Software Center and search for “razorqt.”
After installation, log out, then log back in. Be sure to select Razor Desktop from the Session menu.
You’ll see this small window after the login screen. What the system requires is a window manager to work with. Razor-qt can use any window manager. Your choice here will depend on what your distribution is using. Click on Other… and then on the OK button.
Ubuntu uses the Lightdm window manager. You will, however, not find it under /usr/bin, but rather, under /usr/sbin. So you need to change the directory here.
Now you should be in the /usr/sbin directory. The choice should be lightdm-session.
Razor-qt-specific configurations tools are incorporated into the control center.
These two screen shots have been included just to show a couple of the applications that crashed on my test system. Rebooting or login out and then back in fixed whatever bug caused them to crash.