Technology news and Jobs 
Our Blogs Open Sauce Hardy Heron? Hardly
Our Blogs Open Sauce Hardy Heron? Hardly | Hardy Heron? Hardly |
|
| by Sam Varghese | |
| Friday, 25 April 2008 | |
|
Page 2 of 3 There are other bugs like one which involves NetworkManager where manually configuring the network leads to unreversible failure, a problem highlighted by a reader of Linux Weekly News. The same individual pointed to two other showstoppers - one a scheduling bug, apparently due to a wrong kernel option being chosen as the default, and one caused by using PulseAudio as a sound server. Featured Whitepaper
5 Best Practices for Smartphone Support
In the case of the PulseAudio bug, the default device which uses the Advanced Linux Sound Architecture, must use PulseAudio else the applications that use ALSA will fail. Jonathan Corbet, the editor of LWN, had some criticism of Hardy Heron too. One of his plaints was related to a HAL configuration error which caused his laptop's backlight to remain on when it went into suspend and resume mode. He also had some choice words to say about the location of the configuration file for this option - but then this is a subscription only article and while I can't provide a link, it is worth subscribing to read his thoughts. (yes, that's a plug but for a good cause - and in the hope that Corbet will extend my free trial when he reads this!) Corbet was annoyed by the beep and also the blinking cursor, both of which were defaults in the GNOME terminal. In some ways, this illustrates the conflict between long-time users and newbies - Corbet is a geek and veteran user, while lots of the Ubuntu fanboys are yet to sprout hair on their upper lips. On the plus side, Corbet lists the lower steady state power consumption. I've noticed that you have no choice but to use the proprietary nVidia graphics drivers if you want a decent resolution on fairly recent hardware. The default open source nv driver gives me 800 x 600 on a screen which can do 1680 x 1050. After installing the nVidia drivers, rebooting gives me the right resolution - but then after shutdown it reverts back to the 800 x 600. Solution? Uninstall and reinstall the nVidia stuff again, reboot and then do whatever you intend to do. This appears to be related to the use of more recent versions of the xorg server and more recent video cards. The constant need to reboot after every update in Ubuntu is reminiscent of Windows - on my Debian boxes (x86, AMD64 and MIPS), you only need to reboot in the event of a kernel update. No other changes need a reboot. |
| < Next story in category | Previous story in the category > |
|---|
