The Linux Experiment

This post was originally published on October 16, 2009. The original can be found here.

As part of our experiment, everyone is required to try a different desktop manager for two weeks. I chose KDE, since I’ve been using GNOME since I installed openSUSE. However, I’ve found that while trying to get a desktop manager set up one wrong move can cause everything to fall apart.

Switching from GNOME:

This was fairly simple. I started up YaST Software Management, changed my filter from “Search” to “Patterns”, and found the Graphical Environments section. Here I right clicked “KDE Base System”, and selected install. Clicking accept installed the kdebase and kdm packages, with a slew of other KDE default programs. Once this was done, I logged out of my GNOME session, and selected KDE4 as my new login session. My system was slightly confused and booted into GNOME again, so I restarted. This time, I was met with KDE 4.1.

My Thoughts on KDE 4.1:

As much as I had hated the qt look [which I erronously call the ‘quicktime’ look, due to its uncanny similarity to the quicktime app], the desktop was beautiful. The default panel was a very slick, glossy black, which looked quite nice. The “lines” in each window title made the windowing system very ugly, so I set out to turn them off. Its a fairly easy process:

KDE Application Launcher > Configure Desktop > Appearance > Windows > Uncheck the “Show stripes next to the title” box.

Once completed, my windows were simple and effective, and slightly less chunky than the default GNOME theme, so I was content.

Getting rid of the openSUSE Branding:

openSUSE usually draws much ire from me – so its not hard to imagine that I’d prefer not to have openSUSE branding on every god damn application I run, least of all my Desktop Manager. From YaST Software Management I searched for openSUSE and uninstalled every package that had the words “openSUSE” and “branding”. YaST automatically replaces these packages with alternate “upstream” packages, which seem to be the non-openSUSE themes/appearances. Once these were gone, things looked a lot less gray-and-green, and I was happy.

Oh god what happened to my login screen:

A side effect of removing all those openSUSE packages my login screen took a trip back in time, to the Windows 3.1 era. It was a white window on a  blue background with Times New Roman-esque font. After a bit of researching on the GOOG, I found out that this was KDE3 stepping up to take over for my openSUSE branding. Uninstalling the package kde3base or whatever the shit it’s called forced KDE4 to take over, and everything was peachy again.

Installing my Broadcom Wirless Driver

In order to install my driver, I followed this guide TO THE LETTER. Not following this guide actually gave YaST a heart attack and created code conflicts.

KMix Being Weird

KMix magically made my media buttons on my laptop work, however it occasionally decided to change what “audio device” the default slider was controlling. Still, having the media buttons working was a HUGE plus.

Getting Compositing to Work

I did not have a good experience with this. Infact, by fucking around with settings, I ended up bricking my openSUSE install entirely. So alas, I ended up completely re-installing openSUSE. Regardless, to install ATI drivers, follow the guide here using the one-click install method worked perfectly. After finally getting my drivers, turning on compositing was simple:

KDE Application Launcher > Configure Desktop > Appearance > Desktop > Check the “Enable Desktop Effects” box.

From KDE4.1 to KDE4.3

While KDE was really working for me, the notifications system was seriously annoying. Every time my system had an update, or a received a message in Kopete  an ugly, plain, slightly off center, gray box would appear at the top of my screen to inform me. Tyler informed me that this was caused by the fact that I wasn’t running the most recent version of KDE4. A quick check showed me that openSUSE isn’t going to use KDE4.3 until openSUSE 11.2 launches, however you can manually add the KDE 4.3 repositories to YaST, as shown on the openSUSE KDE Repository page.

After adding these repositories, I learned a painful lesson in upgrading your display manager. Do not, under any circumstances, attempt a Display Manager upgrade/switch untill you have an hour to spare,  and enough battery life to last the whole time. I did not, and even though I cancelled the install about 60 seconds in, I found that YaST had already uninstalled my display manager. Upon restart, I was met with a terminal.

From the terminal, I used the command line version of YaST to completely remove kdebase4 and kdm from my system. After that, re-installing the KDE4.3 verison of  kdm from YaST in the terminal installed all the other required applications. However, there are a shitload of dependency issues you gotta sort through and unfortunately the required action is not the same for each application.

KDE4.3

KDE4.3 is absolutely gorgeous, I’ve had no complaints with it. KMix seems to have reassigned itself again, but it assigned itself correctly. Removing the openSUSE branding was the same, but by default the desktop theme used is Air. I prefer the darker look of Oxygen, so I headed over to my desktop to fix it by following these steps:

Desktop > Right Click > Plain Desktop Settings > Change the Desktop Theme from Air to Oxygen.

Concluding Thoughts

Now that all these things are sorted out, I’m surprisingly impressed with KDE, and I might even keep it at the end of this test period for our podcast.

Let me know if you’ve ever had to change desktop managers and your woes in the comments!

This post was originally published on December 23, 2009. The original can be found here.

With the linux experiment coming to an end, and my Vista PC requiring a reinstall, I decided to take the leap and go all linux all the time. To that end, I’ve installed Kubuntu on my desktop PC.

I would like to be able to report that the Kubuntu install experience was better than the Debian one, or even on par with a Windows install. Unfortunately, that just isn’t the case.

My machine contains three 500GB hard drives. One is used as the system drive, while an integrated hardware RAID controller binds the other two together as a RAID1 array. Under Windows, this setup worked perfectly. Under Kubuntu, it crashed the graphical installer, and threw the text-based installer into fits of rage.

With plenty of help from the #kubuntu IRC channel on freenode, I managed to complete the Kubuntu install by running it with the two RAID drives disconnected from the motherboard. After finishing the install, I shut down, reconnected the RAID drives, and booted back up. At this point, the RAID drives were visible from Dolphin, but appeared as two discrete drives.

It was explained to me via this article that the hardware RAID support that I had always enjoyed under windows was in fact a ‘fake RAID,’ and is not supported on Linux. Instead, I need to reformat the two drives, and then link them together with a software RAID. More on that process in a later post, once I figure out how to actually do it.

At this point, I have my desktop back up and running, reasonably customized, and looking good. After trying KDE’s default Amarok media player and failing to figure out how to properly import an m3u playlist, I opted to use Gnome’s Banshee player for the time being instead. It is a predictable yet stable iTunes clone that has proved more than capable of handling my library for the time being. I will probably look into Amarok and a few other media players in the future. On that note, if you’re having trouble playing your MP3 files on Linux, check out this post on the ubuntu forums for information about a few of the necessary GStreamer plugins.

For now, my main tasks include setting up my RAID array, getting my ergonomic bluetooth wireless mouse working, and working out folder and printer sharing on our local Windows network. In addition, I would like to set up a Windows XP image inside of Sun’s Virtual Box so that I can continue to use Microsoft Visual Studio, the only Windows application that I’ve yet to find a Linux replacement for.

This is just the beginning of the next chapter of my own personal Linux experiment; stay tuned for more excitement.

This post first appeared at Index out of Bounds.

Hello again everyone! By this point, I have successfully installed ArchLinux, as well as KDE, and various other everyday applications necessary for my desktop.

Aside from the issues with the bootloader I experienced, the installation was relatively straight forward. Since I have never used ArchLinux before, I decided to follow the Beginner’s Guide in order to make sure I wasn’t screwing anything up. The really nice thing about this guide is that it only gives you the information that you need to get up and running. From here, you can add any packages you want, and do any necessary customization.

Overall, the install was fairly uneventful. I also managed to install KDE, Firefox, Flash, and Netflix (more below) without any issues.

Some time ago, there was a package created for Ubuntu that allows you to watch Netflix on Linux. Since then, someone has created a package for ArchLinux called netflix-desktop. What this does, is creates an instance of Firefox in WINE that runs Silverlight so that the Netflix video can be loaded. The only issue that I’m running into with this package is that when I full-screen the Netflix video, my taskbar in KDE still appears. For the time being, I’ve just set the taskbar to allow windows to go over top. If anyone has any suggestions on how to resolve this, please let me know.

This isn’t my screenshot. I found it on the interweb. I just wanted to give you a good idea of how netflix-desktop looked. I’d like to thank Richard in advance for the screenshot.

Back to a little more about ArchLinux specifically. I’ve really been enjoying their package management system. From my understanding so far, there are two main ways to obtain packages. The official repositories are backed by “pacman” which is the main package manager. Therefore, if you wanted to install kde, you would do “pacman -S kde”. This is similar to the package managers on other distributions such as apt-get. The Arch User Repository is a repository of build scripts created by ArchLinux users that allow you to compile and configure other packages not contained within the official repositories. The really neat thing about this is that it can also download and install and dependencies contained in the official repositories using pacman automatically.

As I go forward, I am also thinking of ways I can contribute to the ArchLinux community, but for now, I will continue to explore and experiment.

Rounding out this little series I took a look at KDE’s video player of choice: Dragon Player.

Dragon Player

For those of you familiar with similar applications such as VLC, Totem or even Windows Media Player, Dragon Player is a simplistic interface on top of quite powerful video playback.

Everyone loves Big Buck Bunny!

Dragon Player’s power comes from the integrated KDE media backend Phonon. What this means for the user is that it is completely compatible with all installed system codecs. Speaking of codecs, Dragon Player prompts you whenever it doesn’t recognize a new piece of media and offers the ability to automatically search and install the required codecs. This works very well and allows you to keep your system relatively free of nonsense codecs you’ll never actually use, instead installing what you need as you need it.

For a KDE application Dragon Player is surprisingly streamlined and doesn’t offer very many configuration options. In fact almost any other video player has more configuration options than Dragon Player. The only real settings I could find were changing how the video playback looks:

Video Settings

And that’s it. No seriously, there isn’t anything else to mention about this application and believe it or not that’s a good thing! This program is designed for exactly one thing and it does it well. If you’re looking for a single use video player application, and you’re not already a VLC fan, I would highly suggest this as an alternative.

More in this series

• The apps of KDE 4.10 Part I: Rekonq
• The apps of KDE 4.10 Part II: Kontact
• The apps of KDE 4.10 Part III: KTorrent
• The apps of KDE 4.10 Part IV: Amarok
• The apps of KDE 4.10 Part V: Kopete
• The apps of KDE 4.10 Part VI: Calligra Suite

LibreOffice? Pfft. OpenOffice? Blah. KOffice? Dead for a while now. Calligra Suite? Now we’re talking!

Calligra Suite

You may be a bit confused as to what Calligra Suite is, in fact you may not have ever even heard of it before now. Essentially Calligra Suite is a fork of the KOffice project from back in 2010 and has now become the de facto group of KDE publishing/office applications, as KOffice isn’t really being developed any more. It consists of the following applications:

• Words (word processor)
• Sheets (spreadsheet)
• Stage (presentation)
• Kexi (visual database)
• Plan (project management)
• Braindump (notetaking and mindmapping)
• Flow (flowchart)
• Karbon (vector graphics editor)
• Krita (digital painting and image editing)
• Author (e-book authoring)

For the purposes of this post I’m going to be going over the first three which I think are the most commonly used day-to-day applications.

Calligra Words

You’ve seen one word processor, you’ve seen them all right? Well maybe not in this case. Calligra Words has quite a different interface than its contemporaries (even counting the new-ish Microsoft Office ribbon interface in that category).

Take that ribbon!

The first thing you’ll notice is that the majority of the buttons and options are located on the right hand side of the interface. Initially this seems quite strange but I suppose if you were working on a large widescreen monitor, as well all should be right?, this makes perfect sense. As you click in the little tabs they expand to reveal additional categorized options. It is sort of like putting the ribbon interface from Microsoft Office on its side.

Side bar in action

While there is nothing inherently wrong with Calligra Words there were times when I found it confusing. For instance there seems to be some places where the application ignores the conventional paradigm for doing something specific, instead opting for their own way with mixed success. A good example of this is formatting the lines on an inserted table. Normally you would simply select the table, go into some format properties window and change it there. Instead Calligra Words has you select the format you want, from the side bar, and then paint it onto the existing table one line at a time. Again not a big deal if you were first learning to edit documents using Calligra Words, but I could easily see people having a difficult time transitioning from Microsoft Office or LibreOffice.

Other things are just strange. For example the application supports spellcheck and will happily underline words you’ve misspelled but I couldn’t find the option to run through a spellcheck on the whole document. Instead it seems as though you need to hunt through the document manually in order to avoid missing anything. I also had the application crash on me when I attempted to insert a bibliography.

Overall I just get the feeling that Calligra Words is still very much under development and not quite mature enough to be used in everyday life. Perhaps in a few released this could become a legitimate replacement for some of the other mainstream word processors, but for now I can’t say that I would recommend it beyond those who are curious to see its unique interface.

Calligra Sheets

Like Words, Sheets shares the sidebar interface for manipulating data.

Example balance sheet template

Most of the standard functionality makes an appearance (i.e. cell formulas, formatted text, etc.) although once again I’m going to have to focus on the negatives here. Like Words I found some of the features very confusing. For instance I tried to make a simple bar chart with two columns worth of data (x and y). Instead I ended up with a bar chart showing both data sets against some random x plane. Try as I might I couldn’t force it to do what I wanted. The program also seemed very unstable for me and crashed often. Unfortunately I became so frustrated with this program that I just couldn’t dive too deeply into its features.

Calligra Stage

Stage is Calligra Suite’s version of Microsoft Office’s PowerPoint or LibreOffice’s Presentation.

Showing one of the included templates

This is the first application of the three that I think really benefits from having the side bar and it makes finding what you’re after surprisingly easy and straight forward. The only weird thing I really ran into was when adding animation to part of the slide. Again you need to select animation, then sort of paint it on kind of like what you had to do with tables in Words.

Like the rest, I think Stage could use some more development and maturity but unlike the other two I think Stage feels much further along (it didn’t even crash on me once!).

Conclusion

If you can’t read between the lines above allow me to summarize my feelings in this way: Calligra Suite is a solid set of applications but one that feels very young and very much still under development. This is not exactly the sort of feeling you want when you are working on a business or time critical document. However I do like some of the things they’ve started here and look forward to seeing where they take it in the future.

More in this series

• The apps of KDE 4.10 Part I: Rekonq
• The apps of KDE 4.10 Part II: Kontact
• The apps of KDE 4.10 Part III: KTorrent
• The apps of KDE 4.10 Part IV: Amarok
• The apps of KDE 4.10 Part V: Kopete

What does KDE offer for instant communication with your co-workers and friends? Kopete steps up to be your all-in-one IM solution.

Kopete

Kopete provides a KDE integrated instant messaging experience that aims at reducing the number of other instant messaging clients you need to run simultaneously in order to stay in touch with your friends. Rather than running a client for Yahoo Messenger, Facebook chat and Windows Live Messenger, you can instead fire up Kopete, add all of your accounts and take advantage of a single unified interface for all of them. This drastically reduces the on-screen clutter.

Kopete supports a lot of different networks!

The process by which you actually configure all of these accounts is also very straight forward. In fact the first time you start Kopete up (and every time thereafter that you wish to add a new account) you get this nice little interface that helps walk you through the process.

Adding a new account

Once through that easy process you are taken to the main Kopete interface screen where it allows you to view your online friends and, of course, chat with them.

Main contacts screen

Not that it should come as any surprise to anyone familiar with KDE but Kopete also supports quite a bit of customization. You can adjust any of the standard settings that you would expect (i.e. auto-away time out, ‘now playing…’ song statuses, etc.) as well as the general look and feel of your conversations.

With this much customization you’re sure to find something that works for you

While I don’t have much bad to say about Kopete I should point out a couple of its more obvious deficiencies. For one Kopete has no Skype support. Skype is fast becoming one of the most popular instant messaging platforms and its absence is a bit disappointing.

Secondly Kopete varies from being just an acceptable, somewhat decent instant messaging client to being a great instant messaging client, all dependant on which IM network you are using. What I mean by this is basically that Kopete is designed to be a very generic IM client  in order to support as many networks as possible, and that’s fine. However because of this design choice it rarely excels at being the best IM client for networks which handle more than just simple text messages. There are many times when the official client for a given IM network will support many more features than Kopete.

Neither of these should deter you from using Kopete (or at least giving it a try). Like all of the other applications I’ve written about in this series, Kopete offers a KDE feeling and integration to your day-to-day applications and for some people that could be far more worth while than having 100% of all features.

Update: as pointed out in the comments this application is actually now known by the name KDE Telepathy. Sorry for the confusion.

More in this series

• The apps of KDE 4.10 Part I: Rekonq
• The apps of KDE 4.10 Part II: Kontact
• The apps of KDE 4.10 Part III: KTorrent
• The apps of KDE 4.10 Part IV: Amarok

Ready to rock out with KDE’s premier music management application? Let’s rediscover our music with Amarok.

Amarok

I have to start by first admitting that I’ve actually run Amarok once or twice in the past, but sadly could never really figure it out. This always bothered me because people who can figure it out seem to love it. So I made it my mission this time around to really dig into the application to see what all the noise was about (poor pun intended).

Rediscover Your Music

Starting with the navigation pane on the left hand side of the screen I drilled down into my Local Music collection. For the purposes of testing I just threw two albums in my Music folder.

The navigation panel

Double clicking Local Music opens up a view into your Music folder that lets you play songs or search through your artists and albums.

Local media list

When you play a song the main portion in the center of the application changes to give you a ton of information about that track.

Automatically pulls lyrics and other information from the web

This is actually a pretty neat feature but also has the downside that its not always correct. For instance when I started playing the above song by the 90s band Fuel I ended up getting shown the following Wikipedia page about fuel (i.e. an energy source) and not the correct page about the band.

I don’t think that’s right…

Placing a CD in the computer caused it to appear under Local Media (although under a different section). Importing tracks was very straight forward; simply right-click on the CD and choose Copy to Collection -> Local Collection. You then get to pick your encoding options (which you can deeply customize to fit your needs).

Pick your encoding format and go

For Internet media Amarok comes loaded with a number of sources including a number of streaming radio stations, Jamendo, Last.fm, Librivox.org, Magnatune.com, Amazon’s MP3 store and a podcast directory. Like most other media, Amarok also tries to display relevant information about what you’re listening to.

Internet Radio on Amarok

There are loads of other features in Amarok, from its excellent playlist support to loads of expandable plugins, but writing about all of them would take all day. Instead I will wrap up here with a few final thoughts.

Is Amarok the best media manager ever made? To some maybe, but I still find its interface a bit too clunky for my liking. I also noticed that it tended to take up quite a bit of RAM (~220MB currently) which puts it on the beefier side of the media manager resource usage spectrum. The amount of information that it presents about what you’re currently listening to is impressive, but often times when I’m listening to music I’m doing so as a background activity. I don’t foresee a situation where I would be actively watching Amarok in order to benefit from its full potential as a way to ‘rediscover my music’. Still, for at least its deep integration within the KDE desktop, I say give it a try and see if it works for you.

More in this series

• The apps of KDE 4.10 Part I: Rekonq
• The apps of KDE 4.10 Part II: Kontact
• The apps of KDE 4.10 Part III: KTorrent

Welcome to another edition of The apps of KDE 4.10. This time around I’m going to be touching on the KDE BitTorrent client KTorrent.

KTorrent

KTorrent represents KDE’s take on what a BitTorrent client should be. It presents a relatively standard interface that reminds me a lot of other fully featured BitTorrent clients such as uTorrent and Deluge.

The main KTorrent interface

Being a KDE application it is also one of the more fully customizable BitTorrent clients out there, although not to the scale of some of the advanced menus seen in Vuze. It allows you to customize various options including things like encryption, queuing options and bandwidth usage. It also benefits from using a bunch of shared KDE libraries. When I checked its memory usage it was sitting at a respectable 16MB which makes it not the leanest client but certainly not the heaviest either.

Settings menu

Similar to Deluge, KTorrent supports a wide array of plugins which allows you to really tailor the program to your needs. In my testing I didn’t notice a way to browse for new plugins from within the application but I’m sure there are ways to add them elsewhere.

Plugins

I have to admit that I actually went into this article expecting to have a lot more to say about this application but the bottom line is this: it does exactly what you expect. If you need to download torrent files then KTorrent might be for you – and not just if you’re running KDE either. Perhaps its because KTorrent covers the bases so well but I actually can’t think of anything that I dislike about it. It’s a solid application that serves a single purpose and what’s not to love about that?

More in this series

• The apps of KDE 4.10 Part I: Rekonq
• The apps of KDE 4.10 Part II: Kontact

It’s been a while since I’ve used KDE, however with the recent rapid (and not always welcome) changes going on in the other two main desktop environments (GNOME 3 and Unity) and the, in my opinion, feature stagnation of environments like Xfce and LXDE I decided to give KDE another shot.

My goal this time is to write up a series of quick reviews of KDE as presented as an overall user experience. That means I will try and stick to the default applications for getting my work done. Obviously depending on the distribution you choose you may have a different set of default KDE applications, and that’s fine. So before you ask, no I won’t be doing another write up for KDE distribution X just because you think its ‘way better for including A instead of B’. I’m also going to try and not cover what I consider more trivial things (i.e. the installer/installation process) and instead focus on what counts when it comes to using an operating system day-to-day.

Rekonq

The default web browser in the distribution I chose is not Konqueror but rather its WebKit cousin Rekonq. Where Konqueror uses KHTML by default and WebKit as an option, Rekonq sticks to the more conventional rendering engine used by Safari and Chrome.

This is not Rekonq, it is Konqueror

Rekonq is a very minimalistic looking browser to the point where I often thought I accidentally started up Chrome instead.

This is Rekonq

From my time using it, Rekonq seems to be a capable browser although it is certainly not the speediest, nor does it sport any features that I couldn’t find elsewhere. One thing it does do very nicely is with its integration into the rest of the KDE desktop. This means that the first time you visit YouTube or some other Flash website you get a nice little prompt in the system tray alerting you of the option to install new plugins. If you choose to install the plugin then a little window appears telling you what it is downloading and installing for you, completely automatically. No need to visit a vendor’s website or go plugin hunting online.

Like most other KDE applications Rekonq also allows for quite a bit of customization, although I found its menus to be very straightforward and not nearly as intimidating as some other applications.

The settings menu

I did notice a couple of strange things while working with Rekonq that I should probably mention. First off while typing into a WordPress edit window none of the shortcut keys (i.e. Ctrl+B = bold) seemed to work. I also found that I couldn’t perform a Shift+Arrow Key selection of the text, instead having to use Ctrl+Shift+Arrow Key which highlights an entire word at a time. At this time I’m not sure what other websites may suffer from similar irregularities so while Rekonq is a fine browser in its own right, you may want to keep another one around just in case.

Browsing the best website on the net

While I haven’t found any real show-stoppers with Rekonq, I still can’t shake the feeling that I’m missing something. I don’t know how to describe it other than I think I would feel safer using a more mainstream web browser like Firefox, Chrome or even Opera. But like any software, your experience may vary and I would certainly never recommend against trying Rekonq (or even Konqueror). Who knows, you may find out that it is your new favorite web browser.

Hi Everyone,

Now that I have a relatively stable environment, I just wanted to write an update of how things went, and some issues that I ran into while installing my desktop environment.

No Sound

Not that I was expecting anything different from LFS, but I had no sound upon booting into KDE. I found this quite strange, as alsamixer was showing my sound card fine. One thing I can tell you, is that alsaconf is a filthy liar. My sound is now working, and it still says it can’t find my card. I’m not sure how I got it working, but here are a few tips.

• Make sure your sound is un-muted in alsamixer.
• Check your kernel to make sure that either support is compiled in for your card, or module support is selected.
• If you selected module supprt, make sure the modules are loaded. For me, this was snd-hda-intel.

Firefox and Adobe Flash

I’m not going to go into too many details about Firefox, as Jake covered this in his post here, but I’d like to note that installing Flash into Firefox was quite easy. All I had to do was download the .tar.gz from Adobe, and do the following:

tar -xvf flash.tar.gz (or whatever the .tar.gz is called)

cd flash

cp libflashplayer.so ~/.mozilla/plugins (make sure plugins is created if it does not exist.)

KDE Crash On Logout

The first time I tried to logout of KDE, I noticed that it crashed. After doing some investigations, I found a solution here. You want to edit your $KDE4_PREFIX/share/config/kdm/kdmrc to reflect the following:

[X-:*-Core]
…
TerminateServer=true

What’s Next?

I’m actually not sure what I’m going to do next. I suppose I should get VLC running on the system, but that shouldn’t be too difficult. I now have a working web browser, flash, and sound, which should be fine until I can get other things working.

Graphics Drivers

Continuing where I left off in my previous posts I now had a somewhat working desktop but a few things still had to be done. For one I am running this on my laptop and while the open source radeon drivers are actually pretty decent they’re just not quite good enough when it comes to power management. Thankfully the Linux closed source drivers are up to the job.

After reading through these two sites I was able to install the closed source drivers and get full control over my graphics card. To be perfectly honest I’m not exactly sure what steps got me to this point but I do know it was a mixture of the two sites.

Wireless Networking

After careful consideration I had come to the conclusion thought I had bricked my wireless. Worse yet after following the guide here (even the parts specific to KDE) I just couldn’t seem to get it to work. Thankfully I stumbled upon this guide which instructed me to install networking components for KDE. Apparently once I had installed this package all was good.

Flash

Flash was actually incredibly easy to install. All I had to do was enter the following command in a root terminal and then restart Firefox.

emerge adobe-flash

Java

Another big install was the official Oracle Java JRE and JDK. To install just the JRE run the command dev-java/sun-jre-bin. If you want the JDK as well then run the command dev-java/sun-jdk. The only weird part about this was that this package is now considered restricted. To work around it simply download the bin file from Oracle and place it in /usr/portage/distfiles before running the command.

More to Come

There is still plenty more to do, like install LibreOffice and figure out why my computer currently can’t play audio CDs. I am however thankful that at this point I am at least a bit better off than some other fellow Linux Experiment participants.

My Desktop So Far

The high CPU load was because I had just finished compiling a bunch of stuff 😛

Do your GTK applications (i.e. Firefox) look like something designed in the 90’s in KDE? I think I can help you.

I installed the latest Firefox, (not the one in the screenshot, I stole this.) and was very disappointed to see something like the following:

Tyler pointed me to the Gentoo guide here, which helped me find out which packages I needed.

If you install Chakra-Gtk-Config, and either oxygen-gtk or qtcurve (make sure to download the gtk2 theme), you will have better looking GTK applications in no time. Note that there are probably tons of other GTK themes for KDE4, these are just some suggestions to get you started.

That is much better.

If you’re going through the Beyond Linux From Scratch guide, and run into this error while compiling qca-2.0.3 (and I assume many other versions of qca), I think I can help.

You don’t seem to have ‘make’ or ‘gmake’ in your PATH.
Cannot proceed.

The fix is relatively easy. Just make sure to have which installed on the machine. Jake found this out the hard way by looking through the configure script. Doing this experiment on Linux From Scratch has really given me an appreciation for distributions that come with basic utilities such as which.

Since which is very difficult to find on Google, here is a link: http://www.linuxfromscratch.org/blfs/view/svn/general/which.html

Yeah… apparently the ability to restart or shutdown your system using a normal user account from within KDE SC is not something that is installed by default. In order to accomplish this you need to compile and install the kde-misc/kshutdown package using the following command from a root terminal:

emerge kde-misc/kshutdown

I also had to create a new file called /etc/portage/package.accept_keywords in order for this to work. Inside that file just put the following text

kde-misc/kshutdown-2.0

For this version of the experiment I have chosen to try my hand at installing Gentoo. Gentoo, for those who don’t know, or who weren’t following Jake’s posts during the original experiment, is a fully customizable distribution where you have to compile and install all of your applications from source code downloads. Thankfully they do offer some excellent package management tools, Portage in particular, that help automate this process.

Preamble

I suppose a bit of background is the best place to start. During the original experiment I ran Fedora which, while having a whole host of issues of its own, was more or less a straight forward experience. Since that time I’ve dabbled here and there with other distributions, Ubuntu, openSUSE, Linux Mint, among others. For this experiment I wanted a bit of a challenge. I now know the basics, and then some, about running a day-to-day desktop Linux system but I still don’t fully understand all of the inner workings that are going on under the hood. That’s where my choice of Gentoo comes in.

Getting Started

I began by following the rather excellent Gentoo Handbook which thankfully got me to the point where I was able to boot my machine, without the installation media, into a kernel that I had personally configured and compiled. To say that this was smooth sailing probably isn’t accurate, but considering what was actually involved in getting to this point, and how quickly I managed to do it, is a testament to how easy the guide actually is to follow along with.

One thing I would stress to Linux users who may want to try Gentoo and are coming from a more user friendly distribution like Ubuntu is to make sure to get a list of hardware before you start. Run lshw in your Ubuntu (or whatever) install and save the output somewhere. This will show you the list of hardware devices and more importantly the drivers required to run them correctly. I ran into a snag early on where my network card wasn’t working even though Gentoo claimed to be loading the drivers correctly. A quick modprobe later of the driver that was shown to be in use from my earlier install, tg3, and I was back and Internet enabled. Sadly even the lshw output didn’t provide a whole lot of direction when it came to picking and choosing some of the more obscure configuration options for my kernel.

The Challenge

So what do you do when you can finally turn your computer on and boot into your kernel? Well install X I suppose. Unfortunately it was this step that caused me more grief than any of the others. You see apparently you’re supposed to remember what graphics card is in your machine before you try and build a kernel that supports it…

Following along with the X Server Configuration Guide I made it all the way up until the point when I had to specify which “in-kernel firmware blobs” I wanted to compile into my kernel. After, literally, hours of compiling X and then a series of trial and error attempts I finally found a combination that seemed to work. For my own reference the only firmware blob I seem to require is

radeon/R700_rlc.bin

The Wait

I finally had a system that could start X and present me with multiple(!) graphical terminals. By this point I had sunk about ~5 hours into this project. Now it was time to try setting up a desktop environment. My two main choices were GNOME 3.x or KDE SC. I opted for KDE for two reasons:

1. I hadn’t used KDE 4.x in a couple of releases and didn’t mind it last time I had tried it
2. I have yet to try GNOME 3.x but since it is quite the departure from the 2.x series I figured I would go with what I know for now and maybe try GNOME 3.x later

Pulling up the Gentoo KDE guide I began my compilation of KDE SC.

emerge -av kde-meta

More than 400 packages needed to be compiled and installed. My system, a Core2Duo at 2.4Ghz and 4GB of RAM, took approximately 24 hours to finish this single process. Gentoo is certainly not a system that you can expect to have up and running in an afternoon if you’re expecting to have a fully working desktop environment.

Miscellaneous

USE Flags are ridiculous. I understand the concept for them but the fact that you have to continuously add to this list in order to compile programs you explicitly told it to install is a bit much. If you don’t know what a USE Flag is consider yourself lucky. For those thinking about installing Gentoo, don’t worry you’ll know soon enough.

Be sure to change the root password and add any user accounts after you chroot into your new installation. Otherwise you’ll end up like me and boot into a system that you can’t log into!

Next Steps

Well I’d like to finish setting up my desktop. I now have KDE installed but there seems to be some missing components that I hope won’t require a re-compilation… I’ll let you know how that turns out. I also need to sort out my wireless card and get that working. But hey at least for now I can browse the web in my new installation!

As noted in my previous post I have decided to try out a mini experiment wherein I test out three recently released distributions (Kubuntu 10.10, Ubuntu 10.10 and Linux Mint Debian Edition) giving each 48 hours to leave me with either a brilliant or terrible first impression. First on the docket was Kubuntu 10.10.

Install

Kubuntu’s installer is absolutely beautiful. It is simple, sleek and gorgeous. As you work your way through the very simple wizard system it begins to copy files in the background which makes the whole install process much faster than in previous iterations. I’m not exaggerating in the least when I say that this is perhaps the best Linux installer I have ever used.

‘New’ Desktop

When I first booted into the desktop I was very pleasantly surprised. I haven’t used KDE since version 4.3 when I had given up on it because, while beautiful and functional, there were just too many rough edges. It seems to be an Internet cliché at this point but I am going to throw it out there anyway: KDE 4.5 is the KDE release you have been waiting for. Most, if not all, of the rough edges that have plagued the 4.x series in the past have been ironed out and replaced with extremely user friendly, soft and presentable windows and options that just make sense.

For instance the new network connection interface is stupidly simple. If you can’t figure out how to connect to a network (hint: you just click on it) perhaps you shouldn’t be using a computer in the first place.

All of these refinements are accented by the new notification system that not only provides a universal area for all program events, but also fixes almost all of my complaints about the previous versions. You can now scroll through the notifications, instead of watching them grow off-screen, and you can even filter by the individual applications that are generating said notifications. Think of it like a unified e-mail inbox versus individual account inboxes.

Along similar lines the new, subtle, system tray notifications are simply awesome. Take a look at this screen-shot of the animated file copy indicator.

Its a bit hard to see in the screen-shot but the white pie in the upper right is actually the progress indicator. Unlike in GNOME where you get either a file copy dialog, or a motionless tray icon, I now have no clutter and yet full functionality. You couldn’t make a better system for displaying the information needed. “But what if I want to see more information?” Like everything else, this indicator is fully integrated into the notification system and a single click brings up the progress bar and file copy information. I suppose the point that I’m trying to get across is that this KDE release has done a lot of work in doing away with the clutter that you don’t really care to see 9 times out of 10.

Driver installation is once again handled by jockey, just like in Ubuntu. This time however I had absolutely no issues with it crashing or just not working unexpectedly.

‘New’ Software

I also decided to try out the default software selection to see what had changed. Plus I figured this would be a non-bias way to get a real first impression/feel of the distribution.

Software Management

KPackageKit has always been a sore part of (EDIT: the KDE SC) Kubuntu for me. It ‘worked’ but it was far from intuitive, helpful and, sometimes, even useful. The new KPackageKit is an entirely different story. It is far more like a mix between Synaptic and the Ubuntu Software Center and it pulls it off beautifully.

You can now browse by category or search by application (not just package) name. In addition it now also features a list of installed software which is something so painfully obvious that it is hard to believe that this functionality hadn’t existed previously. These three changes alone have completely reinvented KPackageKit in my opinion. I now almost look forward to opening it up to find new software, whereas in previous releases I would go straight to the command line just to avoid it.

Browser

The browser that ships with Kubuntu 10.10 is rekonq 0.6.1, which is essentially a re-spin of Konqueror but instead of using the KHTML rendering engine it uses the faster and more compatible WebKit. While there is nothing overly special about this browser it does feel very Chrome-like and was good enough that I never even bothered to switch to anything else.

One nice thing about it is that it integrates seamlessly into the KWalletManager password store. It also did an excellent job of prompting me to install all of the proprietary codecs so that I could watch YouTube or whatever. The only low point was a lack of a Moonlight plugin but I assume that is probably forthcoming.

Instant Messaging

The default instant messenger is Kopete 1.0.80 which is a fine instant messenger that integrates nicely into the notification system. The real problem with Kopete however is that it simply hasn’t seen nearly as much improvement as the rest of the distribution’s software. If you showed me the Kopete that shipped with KDE 4.3 and the one in KDE 4.5 I couldn’t tell you the difference. From my tests (using the Windows Live Messenger service) I didn’t see anything new. Oddly enough, just like the last time I used Kopete, this version recognizes my laptop’s webcam but there is no option to use it anywhere inside of a chat. Don’t get me wrong, I’m sure a lot of work has been put into Kopete since 4.3 but the problem is I would never know it.

KMail

KMail, now at version 1.13.5, once again takes the e-mail duties for KDE and once again I find it to be far too complicated, cluttered and messy. Sure it is very function and has a boat load of options but at the end of the day I just want to read my e-mail. A good e-mail client should be invisible to the user and KMail is certainly not.

KTorrent

I’ve always liked KTorrent and this release (version 4.0.3) is no different. If you don’t feel like messing around and just want things to work then default settings are perfect. But if you like to tweak your settings at all KTorrent offers every major feature that you’re looking for.

Amarok

I’ll be honest, I don’t really like Amarok and never have. That being said I was determined to give it a fair try and I found it to be a very functional media player. I still do think that it is a bit too complicated for the average person though. What do I mean by this? Well for example why do I have to right click and then choose a menu option to listen to my music? Why doesn’t double click just do it?

One area where Amarok does excel is in its music importing wizard. It is very simple and full of sensible defaults that makes ripping tracks from a CD super simple. Kubuntu ships with Amarok version 2.3.2.

Dragon Player

Like GNOME’s Totem, KDE’s Dragon Player (version 2.0) is a no fuss video playback application. There really isn’t much to say about this as it is a very feature lean and purpose focused player. I do however have to give it a special mention; I never had a single vsync issue while using Dragon Player (even with my troublesome ATI graphics card). Not even VLC can say the same without some fiddling around in the options menu.

Kontact

Kontact 4.4.6 is KDE’s answer to Microsoft Outlook. It provides e-mail, calendar, tasks, RSS and more by basically displaying a single user interface that joins together KMail, Akregator, KOrganizer and more in a single window. While this is an excellent way to achieve the end result it does unfortunately mean that the user experience suffers a bit when each application chooses to do things slightly different from one another. Again this is one area that I didn’t notice much difference from the last time I used it.

Conclusion (Konclusion?)

This Kubuntu release is so much improved its hard to believe it was done by the same people who have worked on the previous iterations (I mean that as a compliment… somehow ;)). If you’ve been put off by KDE in the past or even if you’re just looking for a modern KDE distribution then I highly recommend checking this release out.

Pros:

• A huge improvement over previous releases
• Lots of refinements that make using it a pleasure

Cons:

• Some of the KDE software (not the desktop) could still use some work
• Plasmas are cool and all but I don’t think they are quite as amazing as the KDE team keeps pushing them to be

After a little bit of pressure from the people responding to my previous post (My search for the best KDE Linux distribution), I have finally given in and tried out Chakra. The Chakra Project starts with Arch Linux as a base but, instead of forcing you to build your own distro piece of piece, Chakra comes more or less pre-packaged.

Installation

The installation was one of the best I’ve ever seen. For alpha software this distribution’s first point of interaction is already very polished – even warning me that it is not stable software and might therefore eat my hamster.

The install process even let me decide to install some very useful packages, like Microsoft Core TTF Fonts and Adobe Flash, right away. Even the Language & Time step was incredible, offering a rotating globe that I could drag around and manipulate.

The only issue I had was trying to create a disk partition to install the OS to. This was because I was trying this out inside of VirtualBox, and the virtual hard disk did not have any partitions on it whatsoever. There is a bug and (thankfully) work-around for this known issue with their Tribe installer, and after reading a quick walk-through I was once again ready to install.

The Desktop

The desktop is standard KDE version 4.4.2 after install. Opening up Pacman (or is it Shaman?) showed me a list of brand new software that I could install, including the newest KDE 4.5. One of Project Chakra’s great strengths will be in this rolling release of new software updates. The concept of installing once and always having the most up-to-date applications is very intriguing.

Unfortunately, as with most alpha software, Shaman is still pretty buggy and often crashed whenever I tried to apply the updates. Also unfortunate is that Shaman started a trend of applications simply crashing for no reason. I don’t want to give this distribution a bad reputation, because it is still pre-release software, but I think it goes without saying that the developers have some bug squashing to do before a stable release will be ready. Something I found rather strange is that the current default software selection that Chakra ships with includes two different browsers, Konqueror and rekonq, but no office software whatsoever.

Google Chrome much?

Final Thoughts (for now!)

The Chakra Project looks very promising, albeit very unpolished at the moment. If they can manage to fix up the rest of the distribution, getting it just as polished feeling as the installer, this will definitely be one to look out for. I look forward to trying it out again once it hits a stable release.

As some of you already know, I am a big fan of the KDE desktop environment (or KDE Workspaces or whatever they’re calling it these days). In my search to reach Linux KDE perfection I have tested out a number of different distributions. First there was Fedora, which I happily ran throughout the length of the experiment. Once that was finished I attempted to install and try both Kubuntu and openSUSE. Unfortunately I was unable to do so after openSUSE decided not to play nice. However my search did not stop there, and once the community edition was ready I jumped over to Linux Mint KDE CE. Finally I decided to once again try openSUSE, this time installing from a USB drive. This somehow resolved all of my installation issues.

Now that I have tried out quite a few of the most popular distributions I figured I would write a little bit to tell you fine people my thoughts on each, and why I will be sticking with openSUSE for the near future.

Fedora 11

• KDE Version: 4.2 – 4.3
• Pros: very secure, not too many modifications of the KDE source, cutting edge
• Cons: could have really used some more modifications of the base KDE packages in order to better integrate GTK+, Bluetooth problems, not always stable
• Thoughts:

  I have written at length about my experiences with Fedora during this experiment. Without re-writing everything again here let me simply say this: Fedora is primarily a GNOME distribution and I could never shake the feeling that KDE got the left-over treatment.

Kubuntu

• KDE Version: 4.3
• Pros: very easy to use, nice integration of GTK+ and GNOME notifications, access to Ubuntu support
• Cons: the hardware drivers application (jockey) simply did not work, very bad sound issues, Firefox could not handle opening file types
• Thoughts:

  When I first installed Kubuntu I was thrilled. Ah, this must be what it’s like to use a real KDE distribution, I thought. Everything seemed smoother and far more integrated then it did in Fedora. For example: OpenOffice.org had a KDE theme and it’s file browser actually used the native KDE one. Furthermore the notification system was awesome. Now instead of a GNOME application, like Pidgin, generating GNOME notifications, it instead integrated right into the standard KDE equivalent.

  Then the problems started to show up. Oh I’ll just download this torrent file and… hmm Firefox doesn’t seem to know what to do with it. Why can’t I set the file type options inside of Firefox for torrents? Why doesn’t it use the system defaults? Then the sound issues came. YouTube stopped putting out audio all together and all of my attempts to fix it were futile. Maybe it’s just my hardware but Kubuntu just could not handle multimedia at all.

  While Kubuntu is definitely one of the better KDE experiences it is by no means problem free.

Linux Mint KDE CE

• KDE Version: 4.3
• Pros: excellent package manager, easy to use
• Cons: sound issues, WiFi issues, is this actually a KDE desktop? there are so many GTK+ applications in it…
• Thoughts:

  After hearing much praise for Linux Mint I decided to give the newly released KDE community edition a go. I must say at first I was very impressed. The package manager was far superior to KPackageKit and even included things like user ratings and comments. It also came bundled with many tools and applications designed specifically for Linux Mint. Sadly very few of these were re-written in Qt and so I was forced to deal with GTK+ skinning almost everywhere.

  Sound issues similar to those in Kubuntu (maybe it’s something in the shared source?) started to crop up almost immediately. Again YouTube just did not work no matter how much I tried to fix it. Finally the WiFi connection was very poor, often disconnected on what seemed like a  specific interval.

  While I think this distribution has a lot going for it I can only suggest the GNOME desktop for those who want to give it a try. The KDE version just does not seem polished enough to be recommended for someone looking for the ultimate KDE distribution.

openSUSE

• KDE Version: 4.3
• Pros: very responsive, a lot of streamlined tweaks, rock solid WiFi, excellent audio
• Cons: slower to boot, uses quite a bit of RAM, too much green 😛
• Thoughts:

  Installing openSUSE seemed like an awful idea. After reading all of the complaints that both Phil and Dave had written over the course of the experiment I have to admit I was a little hesitant. However, I am very happy I decided to try it anyway; openSUSE is an excellent KDE distribution.

  Everything about it, from the desktop to the little helpful wizards, all seem to be designed with one purpose in mind: make openSUSE the easiest, or at the very least most straightforward, distribution possible. YaST, often a major source of hate from my fellow Guinea Pigs, does indeed have some quirks. However I honestly think that it is a very good tool, and something that streamlines many administrative tasks. Want SAMBA network sharing? Just open up YaST and click on the wizard. Want restricted codecs? Just hop on over to openSUSE-Community and download the ymp file (think of it like a Windows exe).

  My time with openSUSE so far has been wonderful. My network card seems to actually get better range then ever before, if that’s even possible. My battery life is good and my sound just plain works without any additional effort. If I had one complaint it would be with the amount of RAM the distribution uses. After a quick reboot it takes up a very small amount, around ~350MB or so. However after a couple of hours of general use the RAM often grows to about 1-1.5GB, which is far more than I have seen with the other distributions. Thankfully I have 4GB of RAM so I’m not too worried. I wonder if it has something to do with the fact that I am running the x64 version and not the x86 version. Perhaps it assumes I have at least 4GB of RAM for choosing the newer architecture.

  Whatever the case may be I think I have finally found what I consider to be the very best KDE Linux distribution. Obviously your results may vary but I look forward to hearing what you think.

This piece was cross-posted over at my person website ‘TylerBurton.Ca‘.

Since the end of The Linux Experiment I have started dual booting my laptop, switching between Kubuntu 9.10 and Windows 7 as needed. While this solves all of my compatibility issues, it does pose some more annoying issues. For example after setting up one operating system just the way I like it I now need to do the same for the other. Furthermore after becoming used to using particular applications under Linux I now have to find alternatives for Windows. Well no more! The KDE guys and gals have ported the libraries to Windows!

Installing

To install KDE on Windows all you need to do is head over to http://windows.kde.org/download.php and grab a copy of the installer exe. This will more or less walk you through the initial setup and then present you with a list of packages you can choose to install. Most applications are there including things like KTorrent, Konqueror, Konversation and more! Simply select them and watch as they are easily installed.

Image Walkthrough

The first screen you'll see when installing	The package list
kdebase-apps includes things like Konqueror	The installer downloads the source and compiles it locally
After installing the applications show up right in your start menu	The final result. Konqueror and KWrite running on Windows

Just a quickie here – if you keep video of any kind on your Kubuntu 9.10 system, you may have noticed that the Dolphin file manager doesn’t show thumbnail previews of video files by default.  Turns out that it’s a very easy (if non-obvious) feature to enable. Simply follow these steps:

1. Open up kPackageKit
2. Search for and install the package mplayerthumbs – it has three dependencies, which include mplayer itself (I use VLC, but to each his own)
3. Back in Dolphin, navigate to Settings > Configure Dolphin > General > Previews Tab
4. Scroll down in the list, and you should be able to see an option called Video Files (MPlayerThumbs) – Check that box
5. Drag the Maximum file size slider all the way to the right, and hit apply

Navigate to a folder that contains video files, and watch as they slowly begin to populate. Be patient though, it can take a few minutes if you have a lot of media. You should also note that it doesn’t work with all WMV files.

Thanks to youTube user gotbletu for the following informative video that I ripped these instructions off from: