Wow, this time upstream actually added it even if it is not the default
and requires a scary "AllowRiskyCriticalPowerAction=true" setting.
Making it the default after HybridSleep and Hibernate but before
PowerOff would make a lot more sense but at least this doesn't require
the users to manually
** Changed in: upower
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be supported
To manage notifications about
** Changed in: upower
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be supported
To manage notifications about
Seconded, this still needs a fix. I repeatedly lost data because my
ubuntu would just shut down instead of suspending.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
I've attached a patch already. I've been running for over a year now
with no issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be supported
To
I would like to add my voice here and say that a patch, either to
upstream UPower or to Ubuntu's version would be much appreciated. I've
lost work several times as neither HybridSleep nor Hibernate work on my
laptop so it simply shuts down, and due to a quirk of the batter
management the delay
I've once again lost my open session because upower has decided a
shutdown is a sensible thing to do instead of just suspending and
allowing me to just find a charger. Please consider this an actual bug
and not just a "Wishlist" item. It's something that deeply frustrates
users continuously.
The attachment "Patch that keeps the defaults unchanged but allows the
setting in the config file" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an
You may also want to consider just having Suspend be a fallback option
before PowerOff. These days users are much more likely to have a laptop
that suspends properly and prefer that to happen and just quickly grab a
charger and continue instead of having their computer do a full
poweroff.
**
Please include at least this patch on the package. It allows setting
Suspend as the action but does nothing if the user hasn't explicitly
done that.
** Patch added: "Patch that keeps the defaults unchanged but allows the setting
in the config file"
** Changed in: upower
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be supported
To manage notifications about this
By the way the actual discussion seems to be this one:
https://gitlab.freedesktop.org/upower/upower/issues/59
And this is the unmerged PR with the simple patch:
https://gitlab.freedesktop.org/upower/upower/merge_requests/11
** Bug watch added: gitlab.freedesktop.org/upower/upower/issues #59
Upstream seems to be ignoring the user's wishes. Would Ubuntu be willing
to take the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be
Thank you for your bug report, it has been reported upstream as well on
https://gitlab.freedesktop.org/upower/upower/issues/23
Which got that reply
'Suspend still uses significant amounts of power, and if you run out of
power and do a hard powerdown when suspended bad things can happen.'
**
14 matches
Mail list logo