Archive

Archive for the ‘Fedora’ Category

Unstable & Not Ready – Uninstalling Fedora 12 24-Hours Later

November 20th, 2009 9 comments

Well it has been 24 hours since I first installed Fedora 12 and I am ready to uninstall it. Even after trying to enable 3D graphics with an experimental graphics driver, because the official ATI is not yet ready, I am still experiencing graphical abnormalities, application crashes, and sluggish performance all over. This is not the kind of experience that I can deal with day after day on my primary machine.

I believe most of these issues are just par for the course with Fedora. By that I mean, the Fedora developers love to live on the bleeding edge of technology and unfortunately this time around they didn’t wait for the basic foundation to be ready before shipping. I’m sure within the next couple of weeks, or months at the most, all of my issues will be ironed out. Until then I am reverting back to trusty “old” Fedora 11.




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.

Fedora 12 Graphics [Update]

November 19th, 2009 No comments

I stumbled upon this news thread which mentioned open source ATI driver support through the use of the mesa-dri-drivers-experimental package. Promptly installing this

yum install mesa-dri-drivers-experimental

and a quick reboot later and my desktop seems to have actual 3D graphics support! It’s not perfect but it will certainly do until ATI gets in gear with their own Fedora 12 release.




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.

Installing Fedora 12

November 19th, 2009 1 comment

With the recent release of Fedora 12 it is high time that I upgrade from my existing Fedora 11 install to the new wonders that surely await me. So I hopped over to google and did a quick search and came across the official documentation to upgrade Fedora. My plan was to try and upgrade to see how it works and then eventually do a full re-install just to clear out any cobwebs that have developed over the past couple of months. Without further ado here we go!

Attempt #1: Upgrade

Because the Fedora repositories now use LZMA as the compression algorithm for packages the first thing I needed to do was upgrade rpm

yum update rpm

Next I needed to add rawhide (the current software repository) to my list of repositories.

yum –enablerepo=rawhide –skip-broken upgrade

Once that was done I ran a simple update and was presented with literally thousands of updates.

That's a lot of updates!

That's a lot of updates!

Unfortunately this failed a dependency resolution. Doing some more reading I found out that the dependencies might in fact be OK, but that the older version of yum just can’t resolve them correctly. So I tried updating yum to see if that would make a difference.

yum upgrade yum

Trying once again I was met with utter failure. Still unresolved dependencies! Turning back to the Internet I found out that Fedora actually maintains a separate set of instructions which include the use of a graphical upgrader! Entering:

yum install preupgrade

preupgrade

and I had the upgrade wizard running on my screen. A couple of quick clicks and I was off to the races. I started the download phase and went to bed as I figured it could take a while to complete.

In the morning I was presented with a dialog telling me to restart, which I did. On the next boot a Fedora installer appeared and began to fully install the system. All was going well until disaster struck.

There was an error running your transaction for the following reason(s): insufficient disk space.

Clicking the details arrow gave me more information saying that

You need more space on the following file systems:

18 M on /mnt/sysimage/boot

With no other options I clicked Exit Installer and hopped for the best. Eventually I had to hit the power button on my computer to restart it. Thankfully this allowed me to reboot into my existing Fedora 11 install.

Attempt #2: Re-Install KDE Live CD

After giving up on trying an upgrade I decided to simply download the newest version of the Fedora 12 x64 KDE Live CD. Unfortunately rather than being a smooth installation I had the installer itself crash on me at least 4 different times. Figuring it might be an issue with the x64 version I even tried installing from the Fedora 12 x86 KDE Live CD which ultimately had the same issues. All of these attempts had trashed the data on my hard drive – good thing I did a back up first!

Attempt #3: Re-Install DVD

Getting frustrated I then turned to the old trusty DVD install which I had used previously to install Fedora 11. The unfortunate part about installing Fedora this way is that it defaults to a GNOME desktop. Yes, true, you can select KDE from the installer but last time I did that I got a hodgepodge of KDE with GNOME apps everywhere. Even my network manager was a GNOME application.

Being very careful I inspected the package selections and tried to make this install as KDE-ish as possible. I noticed that even after selecting KDE as your desktop environment, Fedora defaults to installing the GNOME network manager so I deselected that and found knetworkmanager instead. I also added a few other programs, themes, icon sets, etc. that I thought would be useful. Finally I added Armacycles Advanced for install, because honestly it’s great.

If you haven't played it DO IT NOW

If you haven't played it DO IT NOW

Hitting Next the install began. 2,074 packages and counting…

A quick reboot later and I was presented with the install and configuration wizard where I set up my user accounts and system date & time. The install was a success.

Not Problem Free

My install, while complete, is not without its fair share of problems. The graphics module that I had been using with great success under Fedora 11 is just not present in Fedora 12. I googled the problem and it seems that they have yet to release a version for Fedora 12. Without proper graphics drivers my system stability is suffering greatly.

In addition KPackageKit is incredibly slow for some unknown reason. It’s slow to launch, slow to respond, and slow to close. I hope this is something that can be rectified shortly.

Other than that I don’t really have many complaints. The boot time on this version of Fedora is much faster and I can only assume with the new 2.6.31.5-127 kernel that the overall hardware compatibility has improved as well.

Stay tuned for my first impressions in a later post.

My New Desktop

Here is my new desktop. If you look closely you can even see some of the graphical issues that plague my system.

Here is my new desktop. If you look closely you can even see some of the graphical issues that plague my system.




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.

Twelve to twelve

November 5th, 2009 3 comments

Well, it’s official – twelve more days remain until the November 17 release of Fedora 12 (Constantine).  I, for one, can hardly wait – Fedora 11 has been rock-solid for me so far (under Gnome, anyways – but I’ll leave that subject alone) and I can only imagine that Fedora 12 is going to bring more of the same my way.

Among some of the more notable changes being made that caught my interest:

  • Gnome 2.28 – the current version bundled into my Fedora 11 distribution, 2.26.3, has been nothing but amazing.  Unflinchingly stable, fast, and reliable – it’s everything I want in a desktop environment.
  • Better webcam support – not sure how this can get any better from my perspective since my LG P300′s built-in webcam worked straight out of the box on Fedora 11, but I’m interested to see exactly what they bring to the table here
  • Better IPv6 support – since our router does actively support this protocol, it’s nice to see Fedora taking charge and always improving the standard
  • Better power management – for me, this is a major headache under Gnome (I know, I know…) since it really doesn’t let me customize anything as much as I would like to.   Among other things, it’s supposed to offer better support for wake-from-disk and wake-from-RAM.  We’ll see.

I’m sure that Tyler and I will keep you posted as the due date gets closer, and especially once we’ve done the upgrade itself!

Making glut.h work in Fedora 11

November 2nd, 2009 3 comments

As part of a computer graphics course I am taking at university I need to be able to develop C/C++ applications using openGL and the openGL Utility Toolkit (GLUT). I tried using many different C/C++ IDEs, including Eclipse, before I finally settled on MonoDevelop as my IDE of choice. After trying for some time to get this to work in a way similar to what I am used to on Windows, I finally gave up on the compilation errors and consulted the GOOG. As this all actually happened about 2 weeks ago I am a little cloudy where I discovered this tidbit of information but it turns out that even after you install freeglut through yum,

sudo yum install freeglut freeglut-devel

it doesn’t actually register the glut.h library correctly. Unfortunately due to the aforementioned registration issue, MonoDevelop was unable to load glut.h. I was able to rectify this by creating my own pkgconfig file, glut.pc, and placing it under /usr/lib64/pkgconfig.

Here is what I placed in my custom created glut.pc file that seemed to do the job:

prefix=/usr/include
exec_prefix=${prefix}
libdir=/usr/include/GL
includedir=/usr/include

Name: glut
Description: Mesa OpenGL Utility Toolkit library
Requires: gl glu
Version: 7.6.0
Libs: -L${libdir} -lglut
Cflags: -I${includedir}

So yeah, that’s it! This seems to be a very common problem so hopefully what I have described here works for you as well.




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.

Distribution Upgrades

November 1st, 2009 No comments

As with the release of Karmic Koala, the majority of the other distributions we here at The Linux Experiment have decided to run will also be getting an upgrade. Here is a quick breakdown of what’s to come (in chronological order) to give you a heads up of what you can expect us to be blogging about shortly.

Gentoo – Release Set For: Tonight

OK fine, so technically Gentoo isn’t getting a “major new release” or anything like that but considering the nature of the distribution one could claim that it’s nightly builds are basically the same thing.

openSUSE 11.2 – Release Set For: November 12, 2009

The next step forward for openSUSE is version 11.2. Included in this release of openSUSE are major changes to YaST and zypper as well as a new release strategy whereby all releases are bootable by USB and CD-ROM. Some other incremental improvements in software are:

  • GNOME 2.28/KDE 4.3
  • Firefox 3.5
  • OpenOffice.org 3.1
  • Ext4 is the new default filesystem
  • Support for whole-disk encryption

Fedora 12 “Constantine” – Release Set For: November 17, 2009

Always the cutting edge distribution, Fedora has a massive list of changes for it’s next release. For starters all software packages have been recompiled for i686 which should allow for improved performance, especially on the Intel Atom processor. In addition, all software packages are now compressed with LZMA instead of GZIP which, along with yum presto integration (delta versus full downloads), should offer much faster downloads. Thanks to the newest version of Xorg, spanning desktops (1 desktop on 2+ monitors) is now possible. Other software improvements include:

  • GNOME 2.28/KDE 4.3
  • Firefox 3.5.2
  • PHP 5.3.0
  • Ogg Theora has been updated to the most recent version
  • GRUB now supports Ext4
  • Dynamically rotating wallpapers is now a feature under GNOME
  • NetworkManager has been enhanced to take advantage of Mobile Broadband technologies
  • Bluetooth services are now on-demand meaning they only use system resources when necessary
  • Tons of PulseAudio improvements
  • PackageKit has been improved and can now install software from more places (i.e. right within the web browser)

Linux Mint 8 “Helena” – Release Set For: November 2009

Linux Mint 8 continues the trend by incorporating all of the most recent Ubuntu improvements found in Karmic Koala as well as improving on the Mint specific programs. Specifically Mint improves the boot sequence as well as the Mint tools suite of applications that differentiate this distribution from Ubuntu. The end result should make for one of the most user friendly Linux distributions ever.

Debian 6.0 “Squeeze” – Release Set For: TBD 2010

If you are familiar with Debian’s release cycle then you know that what will become of “Squeeze” is simply what passes muster in the current testing repository. Although this distribution is still quite a ways off, it is promising quite a few interesting improvements including better architecture support and boot performance thanks to parallel processing. kFreeBSD is also now included which makes this the first officially supported non-Linux architecture for a Debian release. While many obsolete libraries are being removed for security reasons many new libraries are also making their first appearance including full IPv6 support. Finally there is preparation going into the packaging formats which will allow for future improvements, including better compression algorithms for smaller download sizes.

It’s going to be a busy month!

Check back soon as we begin our upgrades and blog about our experiences doing so.




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.

Taking Wine for a spin

October 20th, 2009 3 comments

Wine, or W.I.N.E. Is Not an Emulator, is a set of compatibility libraries that allow some Windows applications to run pseudo naively on Linux by mapping Windows API calls to native Linux calls. In the past I have been sort of successful with using Wine but I have never really given it a good go. So I decided that I should put Wine through it’s paces!

Approach

Rather than approach this from an expert’s standpoint I am going to use Wine starting from a novice’s ability and then move up if needed.

  1. Try and run program from graphical shell
  2. Try and run program from terminal
  3. Try and adjust WINE settings to see if I can make it work
  4. Search the web for ideas and consult Wine’s App DB

The Programs

I have selected a number of different applications to test with Wine – some productive software and some games. I have done no research as to the compatibility of these programs under Wine, they just happen to be easy to use for testing, so it’s going to be a surprise for me no matter what happens. As I’m sure you can tell it’s been a while since I’ve played games on my PC…

First thing we need to do is make sure Wine is installed!

How to install Wine on Fedora 11

Technically all you need to do is:

sudo yum install wine

but you might want to install some of the additional packages as well, just in case!

Command & Conquer: Red Alert

Now that EA has released this game as free getting a copy of it was a simple download. Once downloaded and unzipped I mounted it and tried running the autorun script.

Red Alert autorun

Red Alert autorun

Error

Error

Sadly this resulted in the above error. Next I tried opening it using a simple double-click on the SETUP.EXE. This launched the program but gave me the following error message:

5.1 = Windows XP?

5.1 = Windows XP?

1. Try and run program from graphical shell: FAILURE

With that failure I decided to try and run it from the terminal so that I would at least be able to see errors in the print outs.

wine SETUP.EXE

This however only resulted in the same error message.

2. Try and run program from terminal: FAILURE

If this problem is truly related to the fact that it thinks I’m running Windows XP maybe I can change that. So off to the Wine configuration menu I went and lo and behold I found an option to do just that!

You can even set different programs to think they are running on different versions of Windows!

You can even set different programs to think they are running on different versions of Windows!

This time I got a different error message about not being able to find all of the files. I decided to burn the ISO to a disc to eliminate any problems with the way I mounted it. Putting the newly burned disc into the drive and using the terminal to launch autorun.exe made everything work and the installation finished. A simple click of the menu icon and I was playing Red Alert!

3. Try and adjust Wine settings to see if I can make it work: SUCCESS

Command & Conquer: Red Alert Final Result: SUCCESS

Well that wasn’t so bad. Let’s try the others!

SimCity 3000 Unlimited

The first thing I did was pop the CD in the computer.

In goes SimCity 3000 Unlimited

In goes SimCity 3000 Unlimited

Autorun

Autorun

Which promptly gave me this:

Nothing could be that easy...

Nothing could be that easy...

I even tried browsing to the setup exe’s location and running it directly. Still no luck.

Stop teasing me!

Stop teasing me!

1. Try and run program from graphical shell: FAILED

Next I tried to run the game from the terminal. I navigated to the setup folder and ran the exe with wine.

cd /media/SIMCITY3000/SETUP/ENGLISH/

wine SETUP.EXE

To my amazement this resulted in the installer starting correctly! A couple of quick Next button clicks and some typing of my serial key and the game began to install. Exactly 3 minutes later the game was finished installing. I then navigated to the application through the GNOME menubar:

Applications > Wine > Programs > Maxis > SimCity 3000 Unlimited > SimCity 3000 Unlimited

Holding my breath I clicked the button and… nothing. Hmm. Turning back to the terminal I browsed to the location where Wine installed SimCity on my hard drive and ran the program from there.

cd /home/tyler/.wine/drive_c/Program\ Files/Maxis/SimCity\ 3000\ Unlimited/Apps/

wine sc3U.exe

This presented me with the following error screen… about 30 times until I killed it from the terminal.

I just kept on getting this error message... over and over and over and over...

I just kept on getting this error message... over and over and over and over...

2. Try and run program from terminal: FAILED

I looked around in the Wine settings and couldn’t find anything that would be causing the game to fail so miserably so I gave up on this step.

3. Try and adjust Wine settings to see if I can make it work: FAILED

Turning to the web I quickly looked up “SimCity 3000″ on Wine’s App DB. From the look of things SimCity 3000 works with Wine but SimCity 3000 Unlimited does not.

4. Search the web for ideas and consult Wine’s App DB: FAILED

SimCity 3000 Unlimited Final Result: FAILED

Try as I might SimCity 3000 Unlimited just does not work under Wine.

Stronghold

Once again I started by inserting the CD-ROM and tried to run the autorun that popped up.

stronghold

Will this work better than SimCity?

Will this autorun work?

Will this autorun work?

CRAP!

CRAP!

Next I tried once again browsing to the CD-ROM in Nautilus.

Do I run autoplay.exe?

Do I run autoplay.exe?

Or maybe Setup.exe? Or even Stronghold.exe?

Or maybe Setup.exe? Or even Stronghold.exe?

Unfortunately once again no success using the graphical shell.

1. Try and run program from graphical shell: FAILURE

After that, and recognizing the limited success I had with SimCity, I repeated the steps but this time using the terminal. To my surprise the installer appeared!

cd /media/030819_1208/

wine autoplay.exe

A little over 4 minutes later the game finished installing and I was presented with the launch screen. Again I held my breath and clicked on Play. It launched! Holy crap it’s actually working… well… sort of. Something wasn’t quite right so I closed the application and opened up Wine configuration. In that window I checked the box next to “emulate a virtual desktop” and set the resolution to 800×600. Once again I restarted Stronghold… GREAT SUCCESS! It worked flawlessly!

2. Try and run program from terminal: SUCCESS

Stronghold Final Result: SUCCESS

Stronghold proves that Wine is capable of providing a seemingly fully compatible Windows experience.

Notepad++

After a quick download from the SourceForge website I began, again, by trying to run the installer from the graphical shell.

Can you guess what happened next?

Can you guess what happened next?

1. Try and run program from graphical shell: FAILURE

Back to the command line I went and after entering the typical commands I was once again presented with the installer.

cd ~/Desktop/

wine npp.5.5.1.Installer.exe

By this point I honestly don’t know why Wine has a graphical launch option or why it fails so badly. Less than a minute later, using the terminal, Notepad++ was up and running perfectly, albeit with some odd graphical issues.

Notice how the text doesn't look quite right?

Notice how the text doesn't look quite right?

2. Try and run program from terminal: SUCCESS

Notepad++ Final Result: SUCCESS

While not without its odd graphical problems, Notepad++ seems completely stable and quite usable on the Linux desktop.

µTorrent

After three successes I was on a roll and jumped over to the µTorrent website in anticipation of another success.

I’ll save you the details,

1. Try and run program from graphical shell: FAILURE

Turning to the trusty terminal (wow that was a lot of t-words) I started up utorrent.exe with Wine.

wine utorrent.exe

The install went fine and even placed a desktop launcher on my desktop when I clicked the ‘Create Desktop Icon’ box. Running the application proved to be a bit more challenging and when I tried to run it from Wine’s Program Files using the following command,

wine ~/.wine/drive_c/Program\ Files/uTorrent/uTorrent.exe

I was presented with some rather odd behaviour in the form of another installation. In fact no matter what I did I couldn’t get it to work.

2. Try and run program from terminal: FAILURE

Again I poked around in the Wine settings but there just didn’t seem to be anything in there that would help.

3. Try and adjust Wine settings to see if I can make it work: FAILURE

Getting frustrated I turned to the internet, specifically Wine’s App DB, for help. I tried following a number of suggestions but nothing seemed to work. I even ended up on µTorrent’s Wikipedia page but still nothing. On a funny note, Wikipedia lists µTorrent’s platforms as “Wine officially supported”.

4. Search the web for ideas and consult WINE’s App DB: FAILURE

µTorrent Final Result: FAILURE

Try as I might I just can’t get this BitTorrent client to work properly.

Internet Explorer 8

Once again I started by using the graphical shell – although I honestly didn’t believe it would work. And guess what?

1. Try and run program from graphical shell: FAILURE

Following the pattern I tried the terminal next. This started up the application but ended abruptly when IE prompted me saying that “This installation does not support your system architecture (32/64 bits)”. That doesn’t make sense though because the Internet Explorer I downloaded was for x86…

2. Try and run program from terminal: FAILURE

Poking around again in Wine’s configuration proved to be fruitless. There just didn’t seem to be any way to tell it to run the application as x86.

3. Try and adjust Wine settings to see if I can make it work: FAILURE

Finally I turned to the web and searched the App DB for Internet Explorer 8. This made it pretty clear that I wasn’t going to get IE 8 to work under Wine as every version listed, aside from 1.0 and 1.5, had a rating of Garbage – Wine’s worst compatibility rating.

4. Search the web for ideas and consult Wine’s App DB: FAILURE

Internet Explorer 8 Final Result: FAILURE

I guess Microsoft’s iconic browser was just not meant to play nicely with Tux.

Well there you have it

I have put Wine through its paces and while there were quite a bit of failures I am very impressed. Wine might just spark a trip down memory lane with my favorite Windows game classics!




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.

Tips & Tricks for Fedora (and others!)

October 18th, 2009 4 comments

I honestly can’t remember how I stumbled across this website but there is a lot of useful information there. Rather than go through the 14 pages of tips and tricks I will just highlight some that I found to be very useful and let you go to the source for the rest.

NOTE: These are all tips for Fedora 11, but with some simple tweaking you should be able to apply them to your distribution of choice.

Modify the sudoers file

By default your username is not included in the list of those accounts who can use sudo. To change this do the following (altered to use nano instead of vi because I prefer things that way):

su -c ‘nano /etc/sudoers’

Then find the line that says:

root    ALL=(ALL)       ALL

and below it add

[username] ALL=(ALL)      ALL

where [username] is the username you want to allow to use sudo. Press Ctrl+O and Enter to save.

You can test if this worked by running the following command:

sudo whoami

If it worked you should see the word root. From this point forward I will assume you have given yourself the ability to use sudo.

Let yum downgrade

By default yum does not allow you to downgrade, or revert to a lower version numbered package. If you would like to change this run:

sudo yum install yum-allowdowngrade

To use it run this command:

sudo yum update –allow-downgrade

Add an ‘open in terminal’ option to Nautilus

This will let you right-click on directories and select open in terminal.

sudo yum install nautilus-open-terminal

Then just log out, and log back in.

Use the backspace key to go back a page in Firefox

Open Firefox and in the URL bar type:

about:config

Then use the filter box to search for

browser.backspace_action

Right-click on it and select Modify. Change the value from 2 to 0 and press OK. Restart Firefox.

Force GTK programs to use QT in KDE

I actually tried this and it seemed to work just fine. In fact it might solve some of Dave’s problems. In a terminal run:

sudo yum install gtk-qt-engine

Then log out and log back in. Next go to System Settings > Appearance > GTK Styles and Fonts and select KDE style in GTK Applications.

Many more

As I said there are 14 whole pages of similar tips and tricks available at the website. Check them out for yourself!




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.
Categories: Fedora, Free Software, Tyler B Tags: , ,

GNOME slip ups; a KDE perspective

October 15th, 2009 3 comments

Since making my switch to GNOME earlier in the week I have finally settled into my new desktop environment. I must admit that while the transition has been almost completely seamless, and in fact has fixed a lot of my issues, I find myself missing KDE. Without trying to spark the holy war that is the GNOME vs KDE argument, allow me to quickly outline some of the reasons for my homesickness.

Look and Feel

Yes I get it, GNOME is supposed to be stripped down and functional. KDE, on the other hand, is supposed to allow for full customization, sometimes at the expense of clutter. Neither of these however explains why GNOME icons and artwork feel so dated when compared to KDE. Take the following as an example.

See the above? See how the Fedora stock icons are just simple shade jobs? Heck that’s better than most default GNOME icon sets. See how the KDE version has actual work put into it? Time and time again KDE wins points for putting more effort into the artwork. And yes I know that you can completely theme GNOME to ‘make it look pretty’ but why should you have to? Why are the defaults so terrible? Surely there are some open source artists out there somewhere. It’s simple things like this that lead to an overall better feel while using KDE when compared to GNOME.

Interaction

The first thing I did back in KDE was to turn off that single-click to open things nonsense. Once that was done my interaction with the two desktops has been more or less identical. However recently GNOME has been ‘losing’ my touchpad tap-click. When I first boot into the desktop it seems to work just fine, but then after a random amount of time I have to resort to the physical mouse buttons. This is really, really annoying.

Battery Life

I have configured both desktop environments for optimal battery life and have some interesting findings. Perhaps as a result of the sparse power management abilities in GNOME I actually get about a half hour less of battery life compared with KDE. I really do wish GNOME would allow for additional power customization; for example I don’t even know if GNOME scales down my CPU clock when it’s running on battery…

One week and counting

Well that’s it for now. At the end of the day it really is a short list of complaints. If anything new crops up I’ll be sure to write about it, if not you’ll have to wait for our podcast!




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.
Categories: Fedora, Free Software, GNOME, KDE, Tyler B Tags: , ,

The road to GNOME

October 12th, 2009 2 comments

As you know we are all going to be transitioning from our current desktop environment (DEs) to something new. I did a bit of quick research and it seems as though Fedora offers the following DE options: KDE, GNOME, Xfce, LXDE. However because KDE is my current DE I  obviously can’t use that one.

Goodbye KDE, you served me well

Goodbye KDE, you served me well

LXDE

Let me start by saying I didn’t chose LXDE as my replacement. With that out of the way I think LXDE could have a lot of potential given the right scenario for its use. From what I have read, it is an extremely light-weight DE that is mostly menu driven. So much so that you can actually script the right-click menu!

Xfce

I consider Xfce to be GNOME-lite, and I mean that in a good way. It is designed to remove some of the clutter found in more fully-fledged DEs, thus speeding up your ability to be productive. However with my system’s beefy specs and the fact that I have been running KDE this whole time I doubt I need to shed that much DE weight.

GNOME

GNOME is the default desktop for Fedora and something that I had initially passed up in order to differentiate my experience from that of Dana’s. Now though it seems as though GNOME is the best (for me!) alternative to KDE.

Installation

After some quick Googling I found a forum post that described installing GNOME through yum by typing the following command into a terminal:

sudo yum groupinstall “GNOME Desktop Environment”

I could only assume that this means that yum will go out and grab anything that has to do with the string “GNOME Desktop Environment”. So I bravely hit the Enter key only to be presented with a list of 57 packages that needed to be installed for 106MiB worth of download!

Is this ok [y/N]: y

The downloads were actually very quick with an average speed somewhere between 650KiB/s and 1MiB/s. The install process on the other hand took significantly longer. Once it was finished I decided to reboot (just in case!) before switching the session options to load GNOME instead of KDE.

First impressions

Oh god what am I doing here? I am not very good with GNOME. It seems as though the first thing GNOME did was get rid of my pretty KDE log in screen and replace it with a sparse looking GNOME one. Par for the course I suppose. A quick switch of Sessions from KDE to GNOME and I logged in.

My new GNOME desktop

My new GNOME desktop

Once my desktop loaded GNOME presented me with a pop-up telling me to unlock the default keyring. Is this the same as kwallet? Apparently not because I had to keep guessing passwords until I finally hit the right one.

Holy crap! My wireless actually connected without prompting me for the wifi password. That is a feakin’ miracle!

The next thing I did was try and install Compiz, which enables desktop effects for GNOME. This took some work but eventually I got it to work by running the following command:

sudo yum install -y ccsm emerald-themes compizconfig-backend-gconf fusion-icon-gtk emerald compiz-fusion compiz-fusion-gnome yum install -y ccsm emerald-themes compizconfig-backend-gconf fusion-icon-gtk emerald compiz-fusion compiz-fusion-gnome libcompizconfig compiz-gnome compiz-bcop compiz compizconfig-python compiz-fusion-extras compiz-fusion-extras-gnomelibcompizconfig compiz-gnome compiz-bcop compiz compizconfig-python compiz-fusion-extras compiz-fusion-extras-gnome

and then turning on some effects within CompizConfig Settings Manager.

CompizConfig Settings Manager

CompizConfig Settings Manager

Next I had to turn off some stupid default setting that made my file manager open a new window for every folder I browsed into. I don’t know why this was enabled by default but it was awful and had to go.

Why GNOME? WHY??

Why GNOME? WHY??

To finish things off I quickly install GNOME Do and set it’s theme to Docky at the recommendation of Phil D. And welcome to my new desktop!

Is this Mac OSX?

Is this Mac OSX?

Differences

I haven’t had a long time to play with GNOME on Fedora yet but I will certainly be comparing it to KDE along the way. So far from what I’ve seen GNOME seems to be a little bit snappier. Another thing I noticed was that while both KDE and GNOME can mount Windows shares, GNOME can’t seem to write to them for some reason. I actually quickly booted back into KDE to make sure this wasn’t just a fluke and sure enough KDE could still write to those same shares. On the plus side KDE now also remembers my WiFi password!

2 weeks and counting…

That’s all for now. In the two weeks leading up to our next podcast I will continue to post about new discoveries and little differences between GNOME and KDE. Until then…




I am currently running a variety of distributions, primarily Linux Mint 17.
Previously I was running KDE 4.3.3 on top of Fedora 11 (for the first experiment) and KDE 4.6.5 on top of Gentoo (for the second experiment).
Check out my profile for more information.