| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit 5af9d52eb562250d7240ac3489a25c743f68b656)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support for two new thumbnails directories named "x-large" and
"xx-large" were added to the XDG thumbnail-spec in 2020 and to
gnome-desktop in GNOME 40. They started to be used by nautilus in GNOME
43 to have larger/sharper thumbnails on HiDPI screens.
But the housekeeper never got updated, so the thumbnail cache has
unbounded growth. I realized this problem when I was trying to debug a
low disk space condition, and realized that my thumbnail cache was 10GiB
in size.
Add the new directories. They're only added to the XDG cache path, since
any application new enough to generate these thumbnail sizes would be
using that path.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The theme is considered deprecated in favor of symbolic icons from
the regular theme.
|
|
|
| |
It was dropped in https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/3970e5c8383caa762e549f9b9931705c80bb6bd4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
g-signal is not fired on property changes, so nm_signal is never called,
and all changes of NetworkManager's WwanEnabled property are missed.
That leads to an inability to disable the airplane mode on laptops with
WWAN after the airplane mode was once enabled by button.
Fix this by subscribing to g-properties-changed to actually listen to
the updates of WwanEnabled. It also makes the code simpler.
The bug was caused by a breaking change in NetworkManager [1] when it
deprecated the custom signal in favor of the standard PropertiesChanged
on org.freedesktop.DBus.Properties, and gnome-settings-daemon still used
the old one. The standard one is supported since NetworkManager 1.2.0,
as noted here [2].
[1]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
[2]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f
Fixes: d74b6de142a2 ("rfkill: watch and set NetworkManager wwan-enabled")
|
|
|
|
|
|
| |
Otherwise it will be called uninitialized when auto suspending.
Fixes #736
|
|
|
|
|
|
|
|
|
|
|
| |
Claiming the light sensor can take a noticeable amount of time when the
sensor is being polled constantly (e.g. via monitor-sensor).
Due to the function being invoked in backlight_enable this can lead to a
noticeable delay when unblanking via key press. Fix this by claiming the
sensor async.
Fixes: https://gitlab.gnome.org/World/Phosh/phosh/-/issues/915
|
|
|
|
|
|
|
|
|
|
|
|
| |
gsd-smartcard currently checks for the insertion/removal of smartcards
in reader devices which where present at the time gsd-smartcard was
started, but does not account for new smartcard readers appearing
after gsd-smartcard was started.
This patch adds support for checking for the addition of new slots
(i.e. smartcard readers), which is necessary to support devices
like the Yubikey (a "reader" and a smartcard) which may be inserted
after gsd-smartcard was started.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 456696d379ce938445a98ddc7667a3743da7ced8)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 9753c852909065d586422df6e62c0ad76ee7c03e)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Beginning with GNOME 3.28, we began defaulting to sleep after 20 minutes
in order to comply with some European regulations:
https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32013R0801&from=EN
See commit 2fdb48fa3333638cee889b8bb80dc1d2b65aaa4a for details. Anyway,
there is a flaw in our plan: even if we tune the setting to 20 minutes,
this doesn't actually work in practice for manufacturers affected by
these regulations because the system might only *begin* to suspend after
20 minutes have passed, but they are actually required to *finish*
suspending before this time. Additionally, the timeout won't begin until
the system has fully booted into GNOME, which adds additional
uncertainty.
Solution: sleep after 15 minutes. This is reportedly what Ubuntu is
doing for OEM installs. And it's closer to the Windows default of 10
minutes.
https://pagure.io/fedora-workstation/issue/360
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 24929113a0aae885a1535bc9da3af3c7b097d1eb)
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 3af336d2fd663f8158c7dbf301f1c0d1af4efa21)
|
| |
|
| |
|
| |
|