Early adopters bloodied by Ubuntu's Karmic Koala
theregister.co.uk
Early adopters bloodied by Ubuntu's Karmic Koala
1–10 of 35 posts
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#2Just checked my Karmic Koala server. It does have Linux 2.6.31, but maybe that's because I've been aggressive about updating it.
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#3I wonder if this is truly a widespread issue. I've been using Karmic daily since the beta was released a few weeks ago, upgrading its packages to the official release, and I haven't encountered any issues yet. Has anyone here had any of the problems described in the article?
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#4Updated my Advent laptop from Jaunty a week ago, no significant issues. Can't say it's massively better than Jaunty in terms of features or performance though.
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#5I've never seen the register being positive about anything new.
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#6I've never seen the register being positive about anything new.
I've never seen the Register being positive about anything.
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#7I wonder if this is truly a widespread issue. I've been using Karmic daily since the beta was released a few weeks ago, upgrading its packages to the official release, and I haven't encountered any issues yet. Has anyone here had any of the problems described in the article?
I've experienced the flickering screen problem which is caused by a rapidly restarting X server (on nvidia-chipset graphics).
In earlier releases gdm seemed to throttle this after 5 attempts and present a text-mode dialog. By default now all is left to the xorg auto-discovery (no config file), so I assume that this fallback was no longer deemed necessary by the Ubuntu folks.
I resorted to booting the computer with a usb-stick, temporarily disabling /etc/init/gdm.conf (or however that upstart-thing now is called, I forgot), then installing the morally questionable :-) nvidia-binary drivers via envy. Works great so far (under bare metal and via VirtualBox as a guest hosted by Windows7).
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#8The entire article mentions only one bug, which is caused by proprietary drivers. Seems more like FUD to me. And yes I had a smooth upgrade to Karmic-amd64 with proprietary ATI drivers.
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#9The entire article mentions only one bug, which is caused by proprietary drivers. Seems more like FUD to me. And yes I had a smooth upgrade to Karmic-amd64 with proprietary ATI drivers.
I think there's a grain of truth. The forums I hang out on have been flooded with "help!" posts of different descriptions in the last few days.
Re: Early adopters bloodied by Ubuntu's Karmic Koala
#10The entire article mentions only one bug, which is caused by proprietary drivers. Seems more like FUD to me. And yes I had a smooth upgrade to Karmic-amd64 with proprietary ATI drivers.
Ubuntu 8.10 broke Intel drivers, which are OSS. Furthermore Ubuntu ships with restricted drivers manager, which pragmatically installs properietary drivers where needed.
Software vendors have the resposibility to their users to perform regression tests as part of their product. If Ubuntu doesn't want do do that, or do it better, then they shouln't bother to compete with other OSs that do.
I'm saying this after 10+ years of use of Linux on my desktop. The 8.10 issue (after deliberately picking low-powered OSS-driven hardware) made me move to OS X, which I hate, in order to have a continuously working desktop.