Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 21986 ideas, 135057 comments, 2615221 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #1641: Prevent data loss. Don't allow suspend/hibernate on known-to-be-broken setups

bug This idea is a duplicate of Idea #94: Fix Suspend and Hibernate.
Written by FrankQuist the 29 Feb 08 at 18:19. Category: System. Related project: Nothing/Others. Status: New
Rationale
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.
Tags: (none)

14
votes
closed
Solution #1: Auto-generated solution of idea #1641
Written by FrankQuist the 29 Feb 08 at 18:19.
Ubuntu Brainstorm was updated in January 2009. Since the idea #1641 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!
0
votes
closed
Solution #2: 'Test' interface for the first attempt
Written by Peter Ford the 30 Aug 09 at 00:03.
I propose johno's comment from 13 Mar 08 as a solution:

"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. "

I would consider this solution a necessary evil, on the grounds that idea #94 can not be fully fixed as it is dependent on hardware/drivers.

Propose your solution

Attachments
No attachments.


Duplicates


Comments
FrankQuist wrote on the 29 Feb 08 at 19:20
This is not 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.

johno wrote on the 13 Mar 08 at 22:49
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.

aidave wrote on the 7 Apr 08 at 17:24
This is a bad idea, because it doesnt solve the problem, but tries to cover it up.

FrankQuist wrote on the 10 Apr 08 at 21:27
It does not cover it up, it *prevents data loss*. If you prefer to make people lose data so their problems are more visible, I don't want you to be in charge of my computer.

Peter Ford wrote on the 30 Aug 09 at 00:13
I suffered some data loss on my first day of using Linux, when Ubuntu froze while trying to wake from hibernation.

I don't think this problem (covered by idea #94) can ever be fully fixed as it is dependent on hardware, and so solution #2 occurred to me.

Now I have just found that johno has already expressed this, and I merely needed to copy and paste it from his comment!


Post your comment