Posts Tagged ‘upgrade’

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


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 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 Debian Edition.
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.

Testing out Testing

October 13th, 2009 No comments

With everybody switching up their desktop environments this week, I decided that I’d take a shot at installing XFCE on my system. My initial research showed that it is somewhat like a light-weight, highly customizable GNOME. Since I’m running on older hardware, it seemed like the best choice for me. While at it, I also decided to go ahead and move my Debian install from the stable to the testing repositories. In an ideal world, this switch would open the doors to some newer software, alleviating many of the issues that I have had with older software.

Moving to Testing:

Without bothering to do any research, I added the Debian Testing repository to my sources list and told the machine to check for available updates. It immediately found 655 new packages available for installation. Luckily, Debian offered me a handy “Smart Upgrade Manager” and I didn’t have to navigate the upgrade process myself:


After hitting the Smart Upgrade button, my machine chugged away for a few moments, figuring out dependencies and the like, and finally presenting me with a 1289.4MB list of 1570 required packages. Hoping for the best, I hit Apply, and spent the next 2 hours waiting for the necessary downloads to complete. Three episodes of House and an episode of Flashpoint later, at almost 1am, the install process was finally finished. So far, everything seemed alright.

Until I restarted. With the updates applied, my machine booted just fine, and even allowed me to login. Unfortunately, it never made it as far as the desktop. I was presented with a blank grey screen and a mouse pointer (which does work), but no windows, toolbars, or panels to speak of. It seems then, that X11 is working, but that it isn’t launching a window manager of any kind on login. I hit ctrl+alt+F1 and was relieved to find that I still had a terminal, and access to all of my files. But where did my desktop go?

Once at the terminal, I launched Aptitude, to see if there were some broken packages that needed to be fixed. It listed 190 that ought to be removed, and another 6 that ought to be upgraded, including GNOME. Hoping to fix the problem, I told it to get to work, and watched as it attempted to clean up the mess that I had created. That finished, I did what I should have done in the first place, and followed these instructions in an attempt to fix my system by upgrading properly.

This time, everything worked nicely, and within minutes, I was looking at my desktop through the brand spanking new GNOME v2.28.0, just released on September 27th. A solitary hiccup with dependencies required me to completely remove and reinstall the Compiz compositing engine. Friends, I speak to you now from the bleeding edge of the Debian GNU/Linux experience. From this point onward, I will receive the very latest code, just as soon as all release-critical bugs have been addressed. Sweet.

Adding XFCE:

From my newly stable machine, I opened up Synaptic package manager and installed the xfce4 package, which pulled all of the necessary components of my new desktop in as dependencies. I also added the xfce4-artwork package, as it promised a slew of extra pretty desktop backgrounds to play with. After adding Gnome Do, Docky, and playing around with the desktop settings, I arrived at a pretty decent looking desktop:


My first impressions of the desktop are that it seems very solid, fast, and customizable. Unfortunately, it is lacking a few creature comforts, mainly alt-tab window switching (seriously, what the fuck?), and drag-and-drop from menu items to  other windows. Over the next couple of weeks, I’ll give it a solid run, and see if it will become my Desktop Environment of choice.

Edit: After a long look down the tubes, I concluded that XFCE doesn’t support alt-tab, and just enabled the Ring Switcher plugin for Compiz to do the job instead.

On my Laptop, I am running Linux Mint 12.
On my home media server, I am running Ubuntu 12.04
Check out my profile for more information.

Impending Upgrades

October 7th, 2009 5 comments

Here’s another fun little tidbit – today I tried to use Writer seriously for the first time, and realized rather quickly that I was running version 2.1 of same. For those who don’t already know, was close on unusable prior to version 3.x. While it has since matured into a very capable suite of programs, the first few versions were just awful. In particular, I couldn’t get the formatting correct on a numbered list with bullet-ted sub-points.

A quick apt-get -t lenny-backports install did the trick, and removed my system-wide dictionary as a bonus. Now both Icedove (Thunderbird) and Pidgin claim that everything that I type is spelled incorrectly. A quick check with Synaptic confirmed that the aspell package had mysteriously disappeared from my system; when I tried to mark it for re-installation, Synaptic refused, claiming that it aspell depended on a package called dictionaries-common, which wasn’t going to be installed for some unspecified reason. Christ.

Figuring that it was a version issue (since the only thing that has changed on my system is my version of, I tried apt-get -t lenny-backports install aspell. It worked, and also warned me that my upgrade had left about 25 packages lying about that ought to be removed:

bluez-gnome, libmtp7, python-notify, obex-data-server, libgda3-common, python-gnome2-extras, evolution-exchange, rhythmbox, system-config-printer,
libgpod3, gnome-themes-extras, bluez-utils, python-eggtrayicon,, libxalan2-java, python-4suite-xml, libgda3-3,
transmission-common, libgdl-1-0, libxalan2-java-gcj, serpentine, transmission-gtk, libgdl-1-common, gnome-vfs-obexftp

The strange thing is that some of those packages look like they might be required by software other than You know, like Evolution, or maybe Transmission? What the hell is going on here? I’m upgrading to the Testing repositories as soon as I get the chance. Hopefully that will solve some of my old-ass-software issues.

The Magic of Lenny Backports

September 28th, 2009 No comments

This afternoon saw me in a really annoying situation. I was in a coffee shop, wearing a beret, and writing poetry, and couldn’t get a ‘net connection. The coffee shop runs an open network access point, but some asshat in a nearby complex was running a secured access point with the same SSID.

For some reason, my version of the network-manager-gnome package (the older one that shipped with Lenny) could not tell the difference, and I could not get a connection. When I attempted to force a connection, it crashed. Repeatedly.

This being my first experience with anything on Linux crashing, I immediately (and rashly) determined that the problem must lie with my (relatively) old network manager. After all, I was running v0.6.6-4 of an application that had since matured to v0.7.7-1! And my companions, who were running the latest version, were connecting no problem! Of course, this also wasn’t the first set of problems that I had encountered with my network manager.

So upon returning to my domicile (I’ve always wanted to use that word in a sentence), I hit the #debian IRC channel and asked about upgrading to the testing repository, where all of the latest and greatest code is awaiting release as Squeeze, the next version of Debian. Having heard that the code was frozen in July, and that the release was slated for early spring, I figured that by this point, the code there would be fairly mature, and easy enough to use. To the contrary, the members of the channel weren’t comfortable giving me advice on how to upgrade, since in their words, I shouldn’t be considering upgrading to testing unless I understood how to do as much.

With this warning, I was then given instructions on how to update (which didn’t make me feel any better – the last step in the instructions was “be ready for problems”), along with the suggestion that I check out first.

Essentially, this site is an alternate repository dedicated to backporting the latest and greatest code from testing to the last stable version of Debian. This means that, with a simple modification to my etc/apt/sources.list file, I could selectively upgrade the packages on my machine to newer versions.

In fact, I had actually already added this repository to my sources.list file, back when I was working on getting Flash 10 installed. At the time, I just didn’t know enough to understand what it was, or what it’s implications were.

So now, running the newest version of network-manager-gnome, a somewhat more recent version of gnome-do, and clinging to the promise that I can upgrade anything else that seems to have gotten better since the time of the dinosaurs when Lenny was released; my urge to upgrade has subsided, and my commitment to wait out the proper release has been restored.