Comment 386 for bug 59695

This bug has been around for over two years. It has been reported for
over one year.

It's incredibly demotivating. I'm just disappointed with Ubuntu's
organization at this point. There doesn't seem to be any way to
escalate this. It's laughable, and it's embarrassing, and I cannot and
do not recommend Ubuntu anymore. Not only that, I can't, even if this
bug gets fixed, because of the larger issue with structured
communication in the Ubuntu community. There's an obvious breakdown
here, not merely in the bug itself, but in the system used for handling
bugs. Is there a way, in the system that's provided, to change the
system sufficiently to fix that breakdown? What exactly is the problem,
anyways, and how is it fixed? I guess this is a topic that should be
continued elsewhere, though..

> This bug is more than five months old, and it is still not fixed neither
> in Gutsy nor in Hardy?!(?!?!)
>
> I find this horrific, especially because there are multiple well known
> and trivial fixes, not just in this thread.
>
> I would like to point out, that even applying the most trivial fix of disabling the APM power saving (-B 255) on every system by default is a magnitude better than the current state.
> I doubt if any power saving could be achieved by this feature, because on most system something causes a spin-up of the disk either way (syslog, atime writes, journaling etc.).
> And this feature has also nothing to do with shock-protection of the disks, that is the job of HDAPS and similar systems.
> And even when it would save power, losing 1% of battery power is not so bad compared to loosing half the lifetime of a HDD.
>
> Could someone please push any of the fixes upstream?