Hi,
I'm sorry I cannot provide all that information.
I am not a developer, I can't play around with the system with the risk of messing it up. I am just a user.
Is there a way I can upgrade to the development release you're talking about without reinstalling ubuntu from scratch???
And I don't know what an "upstream" kernel is.
I can only say that it happens almost EVERY TIME the system hibernatres automatically when the level of the battery is critically low.
Today it CRASHED while hibernating: I got a black screen with a lot of error messages (the word "stack" appeared) and it got stuck without powering off. When I rebooted it booted cleanly and obviously I lost all my unsaved data.
When I hibernate it manually, most of the times all works fine; but not always: sometimes it does fail.
I also notice that this bug is marked for expiration if no further activity occurs. Well it happens i cannot provide further information and tests, but I don't think it is a reason for closing the bug unless you are SURE it is fixed (in which case I'd like to know how to get the update that fixes it).
This is a very CRITICAL bug that can cause disastrous data destruction.
Hi,
I'm sorry I cannot provide all that information.
I am not a developer, I can't play around with the system with the risk of messing it up. I am just a user.
Is there a way I can upgrade to the development release you're talking about without reinstalling ubuntu from scratch???
And I don't know what an "upstream" kernel is.
I can only say that it happens almost EVERY TIME the system hibernatres automatically when the level of the battery is critically low.
Today it CRASHED while hibernating: I got a black screen with a lot of error messages (the word "stack" appeared) and it got stuck without powering off. When I rebooted it booted cleanly and obviously I lost all my unsaved data.
When I hibernate it manually, most of the times all works fine; but not always: sometimes it does fail.
I also notice that this bug is marked for expiration if no further activity occurs. Well it happens i cannot provide further information and tests, but I don't think it is a reason for closing the bug unless you are SURE it is fixed (in which case I'd like to know how to get the update that fixes it).
This is a very CRITICAL bug that can cause disastrous data destruction.