I don't understand why this is filed against indicator-session. If Hibernate fails, the error message you get (if any) should be the same regardless of whether you triggered it from indicator-session, from the power button dialog, from the battery getting critically low, or any other way. So it doesn't belong in the indicator-session code.
In any case, this bug is fixed in that the menu no longer shows Hibernate when there isn't enough memory. Then again, it doesn't show Hibernate in any other case, either. If we reintroduce the Hibernate feature later, we may need to revisit this.
I don't understand why this is filed against indicator-session. If Hibernate fails, the error message you get (if any) should be the same regardless of whether you triggered it from indicator-session, from the power button dialog, from the battery getting critically low, or any other way. So it doesn't belong in the indicator-session code.
In any case, this bug is fixed in that the menu no longer shows Hibernate when there isn't enough memory. Then again, it doesn't show Hibernate in any other case, either. If we reintroduce the Hibernate feature later, we may need to revisit this.