Getting LauncherFolders up and running on Ubuntu 16.04.4

LauncherFolders (http://unity-folders.exceptionfound.com , https://itsfoss.com/group-apps-unity-launcher-launcherfolders) is a great extension to the unity launcher, in being lightweight abd shipping a lot of bang when it only comes to set up containers organizing your apps. However, obviously the code has been crafted back in the Ubuntu 14.04 era, leaving open issues for installation on more modern Ubuntu releases.

First of all, the official ppa (ppa:asukhovatkin/unity-launcher-folders) will no longer register successfully for security reasons such that one has to ressort back to the original deb installation medium (http://unity-folders.exceptionfound.com/unity-launcher-folders_1.0.3_all.deb).

The next fixes, run the app from the console to see the error messages, are documented in (https://askubuntu.com/questions/934916/ubuntu-launcher-folder-not-working) and (https://ubuntuforums.org/showthread.php?t=2325175 , comment #5):

sudo apt install python-gobject python-pil
gksudo gedit /usr/lib/python2.7/dist-packages/unity_launcher_folders/generateIcon.py
#17 change: "import Image" -> "from PIL import Image"

Getting this far, the app itself comes up and is operable as expected. Pity is but, that the folder pane does not show up when clicking the generated launcher item (though it worked in the preview mode). The launcher item itself is nothing more than some .desktop file in (~/.local/share/applications/Browser.desktop). On inspection, we have this exec entry:

Exec=/usr/share/unity-launcher-folders/drawer.py "/home/anyone/.appDrawerConfig/Browser.pickle"

Giving it another console output run reveals another missing python dependency:


Tackling native screen resolution problems on virtual ubuntu guest installs

I remember a time when virtual box users got stuck when trying to run full screen ubuntu guests on ultrabooks with the (as of that time) unusual screen resolution of 1366×768 pixels. Of course, 1366×768 pixels was quite an esoteric resolution at the times of virtual box 4.0.x or so and the emulated graphics driver was simply not (yet) aware of such a circumstance. However, trying to set up an current ubuntu 12.10 guest on the latest vmware player 5.0.2 environment, targeting another 1600×900 ultrabook full screen resolution, showed up to produce the same issue again and I’m not the very first to learn alike, see the vmware threads for example.

The basic problem, as depicted above, is that the guest os just does’nt see the actual native resolution of the hardware because the emulated graphics driver does not provide or list it on request. It will, on the other hand, be able to run that resolution though. Ever tried to find the missing resolution in your display settings with no luck? Then switched the guest os to full screen and, plop, it is there? Then bounced the guest os and the game starts from scratch (and you get this oversized X error window of unsuccessful attempts to apply the latest resolution setting in ~/.config/monitor.xml)? Welcome at Denny’s!