The Ubuntu community has contributed 12357 ideas, 58479 comments, 1187050 votes
Idea
#1676: Prevent data loss. Don't allow suspend/hibernate on known-to-be-broken setups
|
| |
6
|
|
|
Written by FrankQuist the 29 Feb 08 at 18:46.
Category: System.
Related to:
Nothing/Others.
Status: New
|
|
|
Description
Many users will try suspend/hibernate only to find out that it's broken, won't wake up, or that some things, like net connection or periphals, do not work when returning. This can actually lead to data loss. There should be a list, if there isn't, of problematic hardware, and if it is detected that the user has this hardware, the suspend/hibernate is either disabled (with an explaination given) or gives a warning of the risks.
(I don't see how this is a duplicate. This entry does not call for the issue to be *fixed*, since that would probably yet take a while, but to be proactive in preventing data loss until all issues are fixed.)
Tags:
(none)
Attachments
No attachments.
Duplicates
Comments
|
johno wrote on the 13 Mar 08 at 22:47
|
I think its marked duplicate because it deals with common issues. The challenge here is to actually find out what hardware doesn't work. To do that, you need to try out different combinations and methods and have a testing and reporting mechanism for users to give their results. This is basically the same work as getting it working for many users. So in the end, this goes hand-in-hand with the idea of getting it working for users.
A variation would be to have a "test" interface, where a warning is given before trying suspend/hibernate for the first time to alert users to the issues. Then after successfully going through the test, the warning is removed, and possibly an option to send the results back to an ubuntu server for data-collection.
|
Post your comment
|
|
|
