*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
Unfortunately, Gerry's workaround didn't work for me either, nor any of
the other fixes that have been posted. I find it bizarre that the
problem is being blamed on our hardware and/or BIOS. Even a casual
perusal of the postings for this bug will show that it has affected a
large number of people with different hardware and bios'. The one
common thread among all these people is that the problem began with an
upgrade to a new version of Ubuntu, some to Feisty, some to Gutsy. It
would seem to me that the problem is originating in the code, not the
hardware or the bios. If that is not the case, then perhaps someone can
explain why the problem suddenly appeared on a machine that has had the
same hardware and bios for several years, and has also run Ubuntu
successfully up until the Gutsy upgrade. I really don't understand why
this problem isn't being taken seriously by the developers. As the most
successful Linux OS, and given that the number of computers is predicted
to double to over 2 billion in the next five years, this is hardly the
time to let a bug like this go un-fixed. It would be a deciding factor
to most people trying out Ubuntu for the first time. Don't we want to
attract all those new users to Linux, or are we just going to abandon
them to a world full of windows and gates?
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
