|
Bugzilla – Full Text Bug Listing |
| Summary: | Do not suspend (to ram or disk) when shutdown is imminent | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.2 | Reporter: | Andreas Nordal <andreas_nordal_4> |
| Component: | Usability | Assignee: | Thomas Renninger <trenn> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | bjoernv, fbourdonnec, jeffm, mchang, rjwysocki, suse-beta, werner |
| Version: | RC 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Nordal
2011-06-17 07:13:03 UTC
IMHO this a KDE problem. On the other hand it seems also a user misusage as shutdown is not done if the lid promptly is promptly closed on a modern mobile computer as this will trigger a suspend even if shutdown is running. > this will trigger a suspend even if shutdown is running.
Then, the (obvious) solution is disabling the triggering of suspend before running shutdown.
Call it misusage, but IMHO expecting the user to wait for the computer to turn off is unrealistic.
With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained. Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue. We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users. We're working hard to make openSUSE 12.2 the best openSUSE release yet! *** Bug 776521 has been marked as a duplicate of this bug. *** Bug 776521 describes the same issue on openSUSE 12.2 RC2... Danny did quite some KDE work on (auto-)suspend. I wonder how this is done in Gnome. We should look out for a proper solution fitting for every window manager and not hack in something. I expect this is/can/should be done via dbus and something catching suspend/shutdown events and serialize things. And the initiator of a suspend/shutdown event must be able to handle things properly if the request fails. Google says that sleep events or sent via org.freedesktop.UPower: dbus-monitor --system "type='signal',interface='org.freedesktop.UPower'" While this is more upper level software, Rafael might know about this or may be able to give a hint where to look at. This is not very user friendly, but definitely not critical. Is this still a problem on 12.3? I am rather sure this does not happen on Gnome. If you can still reproduce this issue there I try to grab a laptop and reproduce. Sorry for late reply. I only have desktop now (+ broken laptop) so haven't tested recently. Btw, I think I've seen this on Windows (Vista) too. Ok. Window managers have some own hacks how to handle suspend. Chances that this got addressed meanwhile are high. If no one else gives it a try to reproduce I would like to close this one worksforme or similar. Won't fix for 12.2, this is expected to work on newer distros. |