Skip to main content

Ubuntu 7.04 Alpha 5+ - Updating experiences

I'm writing about how Ubuntu handled an automatic update the week of March 5, 2007. These days the process of keeping your system up to date has evolved considerably so that it is very easy to stay current with fixes and security updates. Essentially your distribution runs a background process with an associated desktop applet that keeps tabs on any updates to your distribution, and alerts you when updates are available. You can then determine if you wish to install them or not. The most important reason for having this feature is security upgrades. Windows in particular has made the importance of this feature quite clear over the years.

Upgrading is not always straight forward. Again, Windows proves the point, most notably with XP SP2. Many IT shops refused to push out SP2 because it broke one or more key internal applications. As an example of this, up until mid-2005, when I still worked for SAIC, SAIC refused to fully install SP2 (although, oddly enough, Lockheed/Martin, to whom SAIC served as a subcontractor on a major program, had no such issues and installed it on all their machines).

Linux distributions have also had upgrade issues along the way. In Ubuntu's case there is the notable failure during an upgrade of xorg.core in Ubuntu 6.06 that broke the X desktop. The disruption was limited in scope and a solution quickly provided. I've not heard or read of anything of that magnitude since. But the ghost of that incident was briefly resurrected last week when I attempted to update a number of packages, three of them related to the X windowing system.

Early last week Update Manager presented 17 new updates, three of them related to X11: x11-common, xorg, and xserver-xorg. These updates were trying to repair the following problem: "revert the "fix" to validate_nice_value, which in fact broke it completely." I was able to install all the packages except those three. When the update manager attempted to update x11-common, the following dialog was displayed.

There was no way to satisfy the dialog. No way to change the value, to move forward. If you canceled the dialog, it resulted in the update being aborted, as shown below. I was never able to install the packages.

Patience, especially in testing, is a virtue. I waited for the solution to be pushed out to the update servers. By Friday the files had been removed, and a new major update was made available (with 149 new updates to existing packages). Fortunately, the update problem was such that the flawed packages would not even install. Regardless, this incident raises in my mind issues of quality control and process. The X subsystem can't be rendered inoperative because of an update mistake, especially for novice users.

All Linux distributions, because they depend upon X, suffer from the same problem; if X fails, there is no other way to correct the problem except from the command line. For seasoned users this is not so much a problem as an aggravation. For novice users or users not used to the command line, this is a real show-stopping problem. I've had similar issues with Suse 10.1 and 10.2, where my dependence on nVidia and ATI video driver kernel modules causes X to crash when the kernel is updated and the video driver module is no longer available on reboot.

I know what to do when this problem occurs, but I said it then and I'll say it now: X needs a fall-back video mode built into the X server that it uses if it fails to successfully boot based on xorg.conf values. Canonical dreams of 'selling' Ubuntu to novice and non-Linux-technically savvy users. Until Ubuntu addresses this issue, it will never be ready for those types of users. Ubuntu needs to be resilient and to degrade, not to be fragile and crash. And in the mean time, folks need to find out what happened (again) with the process producing X updates.


  1. They're working on it :) See:


Post a Comment

All comments are checked. Comment SPAM will be blocked and deleted.

Popular posts from this blog

A Decade Long Religious Con Job

I rarely write inflammatory (what some might call trolling) titles to a post, but this building you see before you deserves it. I've been seeing this building next to I-4 just east of Altamonte/436 and Crane's Roost for nearly 12 years, and never knew who owned it. Today on a trip up to Lake Mary with my wife I saw it yet again. That's when I told her I wanted to stop by on the way back and poke around the property, and photograph any parts of it if I could.

What I discovered was this still unfinished eighteen story (I counted) white elephant, overgrown with weeds and yet still under slow-motion construction. It looks impressive with its exterior glass curtain walls, but that impression is quickly lost when you see the unfinished lower stories and look inside to the unfinished interior spaces.

A quick check via Google leads to an article written in 2010 by the Orlando Sentinel about the Majesty Tower. Based on what I read in the article it's owned by SuperChannel 55 WA…

Be Careful of Capital One Mailings

Capitol One ("What's in your wallet?") sent me a bit of deceptive snail mail today. I felt sure it was a credit card offer, and sure enough, it was. I open all credit card offers and shred them before putting them in the trash. Normally I just scan the front to make sure I don't miss anything; the Capital One offer made me stop for a moment and strike a bit of fear into my heart.

The letter's opening sentence read:
Our records as of December 30, 2009 indicate your Capital One Platinum MasterCard offer is currently valid and active.Not paying close attention during the first reading, I quickly developed this irrational worry that I was actually on the hook for something important, but I wasn't quite sure what. The letter listed "three ways to reply" at the bottom; via phone, the internet, and regular snail mail. I elected to call.

Once I reached the automated phone response system, the first entry offered was '1', to "activate my Capital …

cat-in-a-box channels greta garbo

So I'm sitting at my computer, when I start to notice a racket in back. I ignore it for a while until I hear a load "thump!", as if something had been dropped on the floor, followed by a lot of loud rattling. I turn around and see Lucy in the box just having a grand old time, rolling around and rattling that box a good one. I grab the GX1 and snap a few shots before she notices me and the camera, then leaps out and back into her chair (which used to be my chair before she decided it was her chair).

Just like caring for Katie my black Lab taught me about dogs, caring for Lucy is teaching me about cats. She finds me fascinating, as I do her. And she expresses great affection and love toward me without coaxing. I try to return the affection and love, but she is a cat, and she takes a bat at me on occasion, although I think that's just her being playful. She always has her claws in when she does that.

She sits next to me during the evening in her chair while I sit in mi…