Review: Kubuntu 12.04 LTS "Precise Pangolin"

Main Screen
Well, it's that time of the year again. Canonical just released the spring editions of Ubuntu, Kubuntu, and Edubuntu (and with those have come releases of the officially-recognized derivatives Xubuntu, Lubuntu, and Mythbuntu). Today, I'm reviewing Kubuntu, for a few different reasons.

The first is that this is the last version of Kubuntu that will be officially maintained by Canonical. After the announcement about that over a month ago, the future of Kubuntu appeared to be in flux, but thankfully an announcement was made a few days ago that Blue Systems, the maintainer of Netrunner and primary sponsor of Ubuntu-based Linux Mint with KDE, would also sponsor Kubuntu and would take a couple developers from Kubuntu who were previously at Canonical.
The second is that this is a long-term support (LTS) release, and as this is still going to be supported by Canonical, that means this version will get 5 years of support. To match that, Kubuntu needs to be quite stable and bug-free, so I want to see how well that works out.
The third is that I am looking to replace Linux Mint 9 LTS "Isadora" GNOME with something that will in all likelihood be based in some way upon Ubuntu 12.04 LTS "Precise Pangolin". I want to see how this version of Ubuntu can fill that role.
The fourth is that this is the 500th post on Das U-Blog! I think that warrants a pretty big review like this one.

I tested the 64-bit edition of this as a live USB system made with MultiSystem. Follow the jump to see what it's like.

After the boot menu, I was greeted by a boot splash. Although it is a Plymouth-based boot splash that uses the 5 dots as in Ubuntu, it is customized for Kubuntu and uses a very nice, soft blue background with the Kubuntu logo above instead of the previous darker blue background that looked rather garish. I'm glad to see that change made. After that, I was greeted by the KDE splash screen and then the desktop. But before talking about the desktop, I should say that I noticed that the transitions from the boot splash into the KDE splash screen and from that into the desktop are much smoother than ever before; there are no brief flashes or screen artifacts anywhere now. I have not seen such smooth transitions ever before in KDE anywhere, so I give major kudos to the Kubuntu developers for that. Little details like those do count.

The desktop is vanilla KDE; even the wallpaper is the same, although that itself has changed between versions 4.7 and 4.8 of KDE. But the impression of smoothness in the splash screens carried through the desktop too. The notifications popped up fluidly rather than jerkily as before; the same can be said of the Kickoff menu when it is clicked. It was really a pleasure to use something so slick.

Muon Package Manager
Rekonq is the default browser, but I went ahead and installed Mozilla Firefox using the menu item. Going to YouTube prompted me to install proprietary codecs, and while that did not work last time, it did this time, which is great. Also, my laptop's volume keyboard shortcuts were recognized, which is good.

LibreOffice is the default productivity suite. At version 3.5, it works quite well, and it also seems to load faster than what I am used to seeing. Otherwise, the standard software selection is fairly basic once again.

Dolphin has received a number of improvements in KDE 4.8. Animations are now smoother and nicer, while it has undergone some backend changes as well. Overall, it is just a little nicer to use. The one issue that I had was that although I told it to only open files upon clicking twice and to apply the same preferences for all folders, it would still open some files like video files upon clicking just once. Plus, the pane containing information about files would play things like MP3 audio files but not MP4 video files, which was a little strange.

Mozilla Firefox + KDE Lancelot Menu
Neither Skype nor Google Talk were available in the repositories, so I had to download the appropriate DEB files from the respective websites. When Mozilla Firefox saved them to the system, it didn't know how to open them; worse, though, for some reason it didn't even have a program (i.e. Dolphin) associated with opening the containing folder, which is rather strange. Anyway, I was able to find both files and install them using QApt (the KDE version of GDebi). Skype worked great and was totally stable. At first, I thought Google Talk could not recognize my webcam because in the settings screen of Gmail, all I could see was a black screen for the webcam image, but when I clicked it the image was recognized fine, so that worked well.

After that, I tried installing Mupen64Plus and the F.lux GUI. Both installed fine, but neither one worked. Well, that's not entirely true, because Mupen64Plus could be run from the CLI, but its GUI did not work, and the same goes for F.lux. That's annoying for me at least.

Both the Muon Software Center and the Muon Package Manager have gotten updates. Unfortunately, the former did not work for me much because it wasn't able to show the packages that I searched for, so I used the latter almost exclusively. That's fine because anyway in Linux Mint I use Synaptic Package Manager almost exclusively compared to the Linux Mint Software Manager. The only issue that the Muon Package Manager gave me was that while it was apparently able to install the remaining proprietary codecs when I asked it to do so, it didn't do the job properly. This is supposedly a known bug in this version of Kubuntu, and I was able to solve it quickly by searching for a solution online.

Desktop effects worked well. They seemed to be enabled out-of-the-box, so all I needed to do was enable my own preferred set of effects. Even the effects seem smoother too.
Dolphin + LibreOffice Writer + Desktop Cube
One other thing I did to make myself feel "at home" was to install the KDE Lancelot menu. That worked well, and that also feels a lot more polished in its operation.
Kubuntu used about 700 MB of RAM at idle. That's quite a lot, and that is significantly more than the previous version. Granted, this is the 64-bit edition, so the comparison is not entirely apples-to-apples, but when comparing the RAM usage of 32- and 64-bit editions of other distributions, the difference is only a few megabytes, not a few hundred megabytes. It seems like most of that came from Plasma, KWin, and the KDE Lancelot menu (which apparently uses over 30 MB of RAM at idle, which is a lot for what is just a menu). That's not so good, but then again I didn't really feel like the desktop was slow at all.

Well, that's where my time with Kubuntu ended. The fact that Mupen64Plus and F.lux did not work here where they worked in my tested MATE setup means I would probably go with something that fully meets my needs, and Kubuntu is not quite there. But oh my goodness, Kubuntu is incredibly smooth and polished! That and the fact that most everything else that I care about worked fine means that I can give it my highest recommendation to anyone from newbies to experts. Give it a try; you probably won't be disappointed.
You can get it here.


  1. Mine findings on Kubuntu 12.04 are rather different. I am preparing my review of it. :-)

    1. Oh no! Don't bother doing another review based on a Live CD again.

    2. @DarkDuck: You raised some interesting points. I agree that many of the issues are unacceptable issues for a distribution that's supposed to be mainstream, but it would have been marginally nicer to see solutions too. But overall, it was a great alternative take on Kubuntu. Anyway, thanks for the comment!

  2. 700 megabytes?! Wow.

  3. I originally started with Kubuntu 12.04 Daily Build from a 02/25/12 build. A couple of times, I ran into intermittent issues where dialog boxes would appear, indicating that some back end feature in the Plasma desktop (usually indexed searching) was not working properly. Very early in my testing cycle, the Rekonq Web browser also malfunctioned, but by release it was working great and most of the dialog warning and error boxes disappeared.

    I ran into another problem when my final upgrade, bringing me to the 04/24/12 release was ready. Unplanned, and without any warning at all, the default desktop changed from the way I had it set up, which was with the Classic Style Menu and the classic, traditional "K" menu, rather than the classic slab menu. But when I started, I was greeting with a netbook-oriented Activity Style View!

    It actually worked without any issues, but it took me a couple of days to locate the System Preferences Menu in the Activity View. Once I was able to locate it, I was able to change back to the Classic Style View, and moreover, I was able to use a combination of traditional KDE work spaces and mix in the Activity Views as well.

    I view the combination of traditional work spaces and activities as a great advantage. I suspect that the reason that the final installation update configuration defaulted me to the Activity View was because I am using a laptop computer, albeit a large 17" display laptop, which I always use as if it were a desktop, not a laptop at all. After all, this beast, while a mobile computer, is hardly a laptop - I call it a mobile portable; it's heavy. I can, yes, I really can, put it in my lap, but it's sure a lot easier to use when it's on a movable stand, card table, or other fixture, rather than on my lap!

    For me, then, the Kubuntu 12.04 installation and configuration, upgrading from the daily builds to the final release, had some real surprises in it. My personal opinion is that for upgrades, whatever configurations were previously used ought to remain the default. If it REALLY wants to alter the appearance and function that much, it should at least allow you the choice to make that change or retain the previous behavior. Being able to change it back, but having to research in order to even locate the setting, at least to me, is a significant regression in friendly user behavior. Since KDE gives you the choice, at least make that choice obvious.

    The intermittent dialog box errors still seem to occasionally appear, so there are still some Plasma infrastructure issues looming beneath the surface. Perhaps they are artifacts from the transition from daily builds to release. If that's the case, then the transition configurations are defective and should be fixed.

    I'd give the overall experience a "B" grade. Once it's actually running, it runs quite well; it can be quite disconcerting to unexpectedly encounter the behaviors that I've mentioned, and that's the reason for a "B" instead of an "A" grade.

  4. @DarkDuck: I look forward to reading it!

    @manny: Why not?

    @Anonymous: Yeah, it's a lot.

    @Brian Masinick: I have a feeling that the reason why you ran into those issues was because you started with a pre-release build and then upgraded to the final release in place. While I agree that the system should have preserved your settings, I can't help but think that such an experience should only be expected when upgrading from a pre-release version to the final release. I hope that future updates to your system don't mess around with your settings like that.

    Thanks for the comments!

  5. Well my kubuntu was perfect as I wanted.
    It's awesome and running blazing fast and starting really fast with my ssd.
    I just love it more than windows

    1. @pawan: It's great that Kubuntu has worked out so well for you. Thanks for the comment!

  6. i started to use kubuntu i use it as a window xp programme. when i installed it did not show any installation prograsse bar or any thing only show the kde logo so it make me confuse but after 15-20 minute it was installed. other probleam is after download firefox browser i download a file and open downloaded manager of firefox and right click on the file and open downloded folder the system asked me about the name of progarme insted of open folder

    1. @himanshu pandey: I'm rather confused by your comment. Do you mean that you tried to use Wubi to install Kubuntu within Microsoft Windows XP? Also, the issue with Mozilla Firefox may have to do with KDE integration; Mozilla Firefox may not have a proper setting for a program (Dolphin) to open folders, so instead of opening the folder, it is asking you to choose a program with which to open the folder, so you will probably have to navigate to "/usr/bin/" and select "dolphin". Anyway, thanks for the comment!

    2. ya u are right i installed using wubi. but the whole installation process it show only kde kogo nothing else but thanks god it was installed after 15-20 minute. Thanks for your advice about firefox. i will try it

    3. @himanshu pandey: I hope it helps, and thanks for the comment!