Ubuntu release quality

When I first installed Ubuntu in 2006, all my hardware worked out of the box.  It needed a few tweaks to run correctly, but it was much easier to get running than other distros I had tried.  I was very pleasantly surprised, and Linux became my primary desktop for the first time.  My computers are still configured to dual-boot with XP, but I barely ever boot into it.

With the last few releases, though, I’ve felt that after “upgrading” my system, it actually gets worse. There are lots of bugs and regressions, and I wonder how this can possibly be an official “release”.  Intrepid was the worst so far: my video card stopped working, my keyboard’s function keys started locking up the screen, session saving doesn’t work, sound system is misconfigured, …  These are exactly the kind of headaches that led me to abandon Linux in the past and go back to Windows.  When I upgrade my computer, I expect the upgrade to fix problems, not cause more.

Is every Ubuntu release worse than the last?  To see if it’s just my own personal experience, I looked through the release polls on Ubuntu Forums and combined them all together into a little HTML percentage bar graph.  The green bar is for the percent of users who found the release “worked flawlessly”, after either an upgrade or clean install. Yellow is for “few things to fix, nothing serious though”. Red is for “many problems that I’ve not been able to solve”.  (The poll questions are the same for each release, and have 1,300 to 5,500 voters each.)

(Updated graphs including Jaunty)

It’s pretty clear that my experience is not unique:

Feisty (1,387)
47% 23% 30%
Gutsy (5,479)
22% 44% 34%
Hardy (4,250)
23% 46% 31%
Intrepid (1,343)
18% 34% 48%

Almost half of Intrepid users experienced “many problems” that they have been unable to solve.

You can see from the original results that the experiences for upgraders and first installers are roughly the same, proportionally.  (47% of Intrepid upgraders had serious problems, while 48% of first-timers had serious problems, for instance.) I’d speculate that this means that the main difference between people who have problems and people who don’t is the compatibility of their hardware.

I don’t know much about the technicalities, and haven’t followed the politics behind release cycles, but it seems that something needs to change in the priorities.  I don’t understand why a product would be shipped out the door as a “release”, when it has major bugs like this that were known in advance.  Isn’t that what betas and release candidates are for?

I’ve been told that I should wait a few months before upgrading, so that when I do, the bugs have been fixed.  But then… what’s the point of calling it an official release?  Why don’t you delay the release until those bugs are fixed?

I’ve been told that I should stick to LTS releases if I want fewer bugs, but I had plenty of problems with the Hardy upgrade, too.  The graph shows that Hardy was only marginally better.  Some even said the LTS release was “much more buggy than Gutsy or any other previous release“.

I’ve been told that Ubuntu’s release schedule is a response to Debian’s long delays between releases — that a rigid six-month schedule keeps programs like Firefox and OpenOffice up to date, but as a consequence we have to pay the price of a less stable system. I don’t understand why these are so intertwined.  I can download the latest bleeding-edge versions of software titles from getdeb.net and run them just fine on my system; why can’t the “flagship” titles be kept up-to-date, while the low-level subsystems are kept as stable as possible?  If I’m using the latest Firefox beta and it crashes, it’s no big deal, but if a less-technical user upgrades their computer and the video card or wireless card stops working, that’s a deal-breaker.

Also, why not keep the release candidates to a rigid schedule, but delay the actual release until the bugs are fixed? Users who just can’t wait for the upgrade can subscribe to the RCs instead of the actual releases, while normal users who want to use their computers instead of debug them can wait until the real release.  Maybe this is what’s supposed to happen with the betas and releases?  It’s not working.

Add a “From:” field to gnome-screensaver locked screen

Just a small idea for improving gnome-screensaver.  When the screen is locked, other people can leave messages, which show up as libnotify pop-ups.  It’s not obvious to the person leaving the message how it will appear, though, so I think we should add a From: field to encourage them to sign their name.  Otherwise you might not know who left the message.

Currently it looks like this:

and the pop-up looks like this:

I think we should add a From: field like this:

and the corresponding pop-up could look like one of these:

After proposing this on Ubuntu Brainstorm, I found an independent request on Launchpad, so I’m not the only one. 🙂


Canon refuses to support Linux

I’d been wanting a scanner for a while, and kept procrastinating.  Eventually I got fed up with myself and drove to Staples and bought a Canon CanoScan LiDE 70.  After getting home, I remembered why I don’t make impulse purchases at stores.

The scanner seems decent, but does not work in Linux, making it useless to me since I switched to Ubuntu.

I wrote to Canon several times asking them to support my OS, and they refuse:

Thank you for your inquiry. We value you as a Canon customer and appreciate the opportunity to assist you.

Unfortunately, Canon does not write or support any drivers or software for the various Linux operating systems. The driver development information is proprietary information, kept at Canon Japan, and is not available to the public. I apologize for any inconvenience this may cause.

Please let us know if we can be of any further assistance with your LiDE
70 scanner.

Thank you for choosing Canon.

I told them that they don’t need to write drivers themselves; they can be written by the Linux Driver Project for free.  All Canon has to do is provide the proprietary communication protocol information, which will not be disclosed, but they refuse to do anything to help:

While considering the desire to provide the best possible support for Canon‘s products, Canon USA must make decisions on which products to provide driver support and platforms to provide drivers for.  Currently, Canon USA has decided to support only the Microsoft Windows and the Macintosh operating systems.

Canon USA has announced no plans to provide or assist in supporting the Linux platform with the consumer line products.  We understand, and sincerely apologize for any frustration this may cause if your are using an operating system Canon USA does not support.

We sincerely apologize for the difficulties and inconvenience this reply may cause. As a Canon customer, your satisfaction with our products and service is very important to us. We are dedicated to doing our best to provide support of our products, warranties, and customers with the support options we have available to us.

We remain committed to gaining your confidence and business once again. If, in the future, you reconsider your decision regarding your Canon scanner, we hope you will provide us with another opportunity to serve you. Until that time, we hope any replacement products perform to your expectations.

Thank you for contacting Canon.

Blah blah standard form response.  Guess I won’t make the mistake of buying their products again.

It looks like there might be hope, as Jürgen Ernst is working on a SANE backend for “CanoScan LiDE 600F”, which would support the LiDE 70, too.  I can understand not wanting to waste employees’ time on a tiny minority OS, but it’s ridiculous that users have to completely reverse-engineer their products’ protocols in order to use them, when manufacturers could very easily make this information available for us to write drivers with at no cost to them.

Kensington VideoCAM

This is super old-school and likely no one has any use for it anymore, but I once mirrored the Kensington VideoCAM webcam Windows 2000/XP drivers from this site, which are no longer available online:

The Unofficial Source for Kensington VideoCAM Support
By Orson Teodoro [horsie619@aol.com]

http://www.geocities.com/trypt0/videocamsupport.html

The text of the website itself is available on the Wayback Machine, but the driver files are not.  So here are the files I have, including a mirror of the original directions and driver list. Links to driver files I didn’t mirror are struck through. (Sorry.)