SDL applications (usually games) don't have any API to provide an
application ID and a reason for inhibition, so if those are Flatpak'ed
get the application ID from the Flatpak, and use the gathered name as
the reason for inhibition.
745b858...
by
Carmen Bianca BAKKER <email address hidden>
Update Esperanto translation
425828e...
by
Hans de Goede <email address hidden>
media-keys: Stop treating tablets specially
There are problems with treating the power-button on tablets in a special
manner:
1) The configuration for the power-button behavior is now part of the
main control-center power capplet, so it is visible to all users. It is
very strange and inconsistent for users with a device which gets identified
as a tablet that they can configure the behavior of the button in the
control-center but the behavior does not change.
2) The method used to determine if something is a tablet is unreliable,
various surface like devices and some laptops wrongly have "Tablet"
as chassis-type. So relying on chassis-type info for this is a bad idea.
This commit removes the special handling of the power-button on tablets,
falling back to the normal behavior of doing what the user has configured.
2e50892...
by
Hans de Goede <email address hidden>
power: Stop treating tablets specially
Quite some time ago special handling for tablets was added to
gsd-power-manager to automatically suspend the tablet when the
screen was blanked to save power.
With the more recent auto-suspend (when on battery power) support, this
hardcoded behavior really is no longer necessary, if the auto-suspend
timeout gets set to the same value as the blank timeout the same result
is achieved, but now under user control, rather then being hardcoded.
Not having this hardcoded is desirable because suspend is not always
desirable, e.g. when ongoing downloads are active, or other network
connections are open such as an irc client.
The hardcoded behavior is especially troublesome because it not only
triggers on actual tablets, but also on various non tablet devices,
both surface like devices, which are often used as one would use a
laptop, as well as on some actual laptops. On laptops one may typically
have an irc-client open, network downloads ongoing, etc. and then lock
the screen when walking away. The current hardcoded suspend behavior
causes the downloads to abort, irc messages to be missed, etc. and
with this not being configurable there is nothing the user can do to
avoid this.
I've looked into making gsd_power_is_hardware_a_tablet() more reliable,
but this relies on the DMI chassis type, which ultimately simply is
unreliable
Since the auto-suspend on screen blank functionality is duplicate with
the auto-suspend and the tablet-identification is unreliable, lets just
remove the special handling for tablets.
c07ea84...
by
Benjamin Berg <email address hidden>
power: Only disable Suspend/Hibernate actions inside VM
While we theoretically only want a different default value inside a VM,
we currently hack this by never doing a suspend action inside VMs.
However, that also breaks automatic logout, which is an unintended side
effect.
Move the check to not install the corresponding timeout (preventing
sleep warnings from being displayed) and also only enforce the VM
specific hack for the Suspend and Hibernate actions.
0339e6c...
by
Benjamin Berg <email address hidden>
color: Add test for always on and shortened smearing time
02295de...
by
Benjamin Berg <email address hidden>
color: Allow night light to be always on
Currently if the user configures the "from" and "to" times for the night
light schedule to be close together or equal, g-s-d gets confused as it
still tries to smear the transition over a full hour period.
To fix this, first make sure that the smearing period is short enough to
fit between sunrise and sunset. Also redefine equal start/end times when
calculating whether a time falls into a range as the full 24h period.
This effectively means that we will smear over the full day or night
time when the sunrise and sunset are closer than an hour to each other.
It also means that we always enable night light when the times are
equal.
Based on a patch by Matthew Leeds <email address hidden>.
