Archives, eh
-
# Hardy Heron
The first thing I noticed when I upgraded from Gutsy Gibbon to Hardy Heron was that for the first time in four upgrades – about two years – it actually worked. Not that it was seamless, I froze up halfway through forcing me to reboot the computer and kick the process off manually from the command line after ten or fifteen minutes of gormless staring at various conf files wondering why I bothered. But after I worked out how to finish the upgrade it more or less worked fine and I could boot to the gnome desktop afterwards.
Year of the Linux Desktop projected to be sometime in 20??.
The second thing I noticed was that Firefox 3 beta 5 (I think it was 5) is the default browser. Wellll, I didn’t exactly “notice”, I knew it was going to be the case. What I noticed was how all my Firefox extensions failing to work. Even when I enabled them, many of them failed to do what they do. Umm…what? Why? Is Firefox 3 so compelling that we’ll go with a beta despite it by definition not being ready for the public? I appreciate that there are longstanding memory use issues that have been worked on in FF3 but the beta breaks my browsing experience.
If only Ubuntu come with a package depository and system update tool that they could have used to roll out Firefox 3 after it was released from beta, a update tool that I could choose not to use until I was happy that my extensions supported the new version.
Anyway. The third thing I noticed was that Hardy Heron isn’t shutting down cleanly on my laptop. It hangs for a moment at a console and then vomits warnings and/or errors. So in fact it didn’t update successfully. Quite sure indeed that it is something to do with my wireless card. I suppose I’ll have to do a clean install afterall. I better start following the ACPI bug for my laptop model now so I can do my clean install after someone works out how to patch the kernel to enable sound.
