E
Ezeloe Blanche Cloeiss
Ubuntu sucks. Instead of moving forward with every release, they have the
uncanny ability to take Linux back in time by piling code that doesn't work
on top of more code that doesn't work until they have turned their OS into a
garbage salad. 8.10 was GREAT, and for the most part everything worked. Some
things were missing concerning support of newer Eees, but then they released
Ubuntu Jaunty 9.04. 9.04 could only have been released completely untested,
as they missed something as stupid as the Intel tiling kernel bug which
caused every Intel card out there to crawl during any OpenGL function. There
is no excuse for their release of alpha grade drivers and less than alpha
grade kernel code into their release distribution.
In order to work around all of the bugs that 9.04 released as "gold"
"stable" code, one must spend at a minimum 30 minutes replacing packages and
patching mtrr bugs to get a reasonable level of performance out of their
Eees. We spent days working on documenting all of the fixes that need to be
applied to 9.04 to get it to some semblance of stable. Even then, don't turn
compiz on and suspend because your super cool new "stable" version of xorg
will consistently segfault leaving you at a GDM screen without your data
being saved in any of the applications it unloads out from underneath
itself.
Now we have Karmic coming down the pike in just a few weeks, and xrandr
can't even take you from 1024x600 to 800x600 even though it thinks it did.
Not only that but since your rfkill devices are re-ordered at boot, the only
way to get the right one is to trigger them both and hope for the best
unless you like nasty greps in something that should respond instantly. When
you consider WIFI if you don't trigger one, sleep, then trigger the other
it's not going to work anyway even though it will think it did. If you
trigger rfkill, but you see that NetworkManager still has your WIFI
disabled, yeah, that's because it's looking at the other one. Oh and don't
put away the force pciehp edit that you put in your menu.list for Jaunty
because even though there's a cool kernel mode setting feature, they still
haven't fixed that bug that's existed since *2.6.28*. No, there is nothing
that I can do about the notifications clogging up your screens, Ubuntu's
shiny new notification system STILL ignores the expiration time option from
notify-send and apparently now defaults to more than 10 seconds before
expiring a notification. Oh and the scripts that live in /etc/pm/power.d
yeah they only trigger sometimes now. So, if you have my utilities installed
in 9.10 and you are wondering why it doesn't trigger to powersave when you
unplug power, you can thank the wonderful Ubuntu team for creating even more
bugs in this "great" operating system by switching to devkit rather than
choosing to stick with something stable and mature.
uncanny ability to take Linux back in time by piling code that doesn't work
on top of more code that doesn't work until they have turned their OS into a
garbage salad. 8.10 was GREAT, and for the most part everything worked. Some
things were missing concerning support of newer Eees, but then they released
Ubuntu Jaunty 9.04. 9.04 could only have been released completely untested,
as they missed something as stupid as the Intel tiling kernel bug which
caused every Intel card out there to crawl during any OpenGL function. There
is no excuse for their release of alpha grade drivers and less than alpha
grade kernel code into their release distribution.
In order to work around all of the bugs that 9.04 released as "gold"
"stable" code, one must spend at a minimum 30 minutes replacing packages and
patching mtrr bugs to get a reasonable level of performance out of their
Eees. We spent days working on documenting all of the fixes that need to be
applied to 9.04 to get it to some semblance of stable. Even then, don't turn
compiz on and suspend because your super cool new "stable" version of xorg
will consistently segfault leaving you at a GDM screen without your data
being saved in any of the applications it unloads out from underneath
itself.
Now we have Karmic coming down the pike in just a few weeks, and xrandr
can't even take you from 1024x600 to 800x600 even though it thinks it did.
Not only that but since your rfkill devices are re-ordered at boot, the only
way to get the right one is to trigger them both and hope for the best
unless you like nasty greps in something that should respond instantly. When
you consider WIFI if you don't trigger one, sleep, then trigger the other
it's not going to work anyway even though it will think it did. If you
trigger rfkill, but you see that NetworkManager still has your WIFI
disabled, yeah, that's because it's looking at the other one. Oh and don't
put away the force pciehp edit that you put in your menu.list for Jaunty
because even though there's a cool kernel mode setting feature, they still
haven't fixed that bug that's existed since *2.6.28*. No, there is nothing
that I can do about the notifications clogging up your screens, Ubuntu's
shiny new notification system STILL ignores the expiration time option from
notify-send and apparently now defaults to more than 10 seconds before
expiring a notification. Oh and the scripts that live in /etc/pm/power.d
yeah they only trigger sometimes now. So, if you have my utilities installed
in 9.10 and you are wondering why it doesn't trigger to powersave when you
unplug power, you can thank the wonderful Ubuntu team for creating even more
bugs in this "great" operating system by switching to devkit rather than
choosing to stick with something stable and mature.