Comment 387 for bug 85488

i've been following this thread for some time now with a mood of increasing depression...

a year ago i was running 6.06 (kubuntu). it was my first experience of ubuntu and i was pretty happy. everything was working ok.

i failed to get 6.10 to install. i must have tried every option there was, but i couldn't do it. so i stuck with 6.06.

i got a new computer at the same time that 7.04 came out. on it went! and, fantastic, i could suspend it, something i could never do with 6.06.

well, a month or so later there was an update to KDE, which i installed using Adept. the next time i started the computer, no KDE at all.

after much googling (using Windows), i found that i had no swap disk, so i had to type some guid into a config file or two somewhere. i got KDE working...but it had no status bar or Start button. it took me more hours and more googling to get it all working again.

in the course of my googling i discovered that this lost swap disk seemed to have been reported as a problem with the suspend functionality. ok then, i won't use suspend any more.

then i needed to use my scanner. everything was black. more google, then go to a Windows machine (much merriment at my expense) to get the document scanned.

so, i have black scans because someone decided to ship a suspend feature that caused me several hours of grief. arrrghh.

i confess that i *assumed* that a bug like this would get fixed PDQ. i really could not believe the discussion in this thread. i've been dipping in every couple of weeks and it never gets any better.

i am not the kind of user to compile my own kernel. i'll happily run some script before starting the scanner, but custom kernels? no way.

i have a common scanner, which worked fine on 6.06. i can understand something getting broken by a new release (after all, Windows does it all the time) but i do expect such things to be fixed. to me, this is more important than adding new features. (why do i need a new feature if it's going to break at the next release?)

jack