On panel construction, we trigger asynchronous creation of a GDBusProxy
for the IIO sensors daemon and one for the Screen g-s-d interface.
Since there's no guarantee we'll have the screen proxy ready by the time
the IIO proxy is constructed, guard for (priv->screen_proxy != NULL), or
we'll hit a critical.
https://bugzilla.gnome.org/show_bug.cgi?id=754735
Orca was not reading this row at all - since the row is
clickable (role 'push button'), orca expects it to have
an accessible name. So, lets set one.
https://bugzilla.gnome.org/show_bug.cgi?id=746756
When the main battery isn't called BAT0, as happens on a dual-battery,
convertible Toshiba laptop, we would tag both batteries as "Extra". Mark
the first one as being the main battery.
In the longer-term, we'll have UPower exporting the exact information
about which is in the "dock" and which is in the same package as the
processing unit, when the kernel exports it.
See https://bugzilla.kernel.org/show_bug.cgi?id=97841https://bugzilla.gnome.org/show_bug.cgi?id=748592
With UPower 1.0, the critical action to take when the battery level
is too low isn't in the hands of the user anymore, but in the hands
of the system.
It's now handled by UPower directly, through the CriticalPowerAction
configuration option. Instead of asking logind whether the system
supports hibernation, remove the action label altogether.
https://bugzilla.gnome.org/show_bug.cgi?id=749436
When a Bluetooth airplane mode isn't available (whether hardware or
software) it means there are no Bluetooth adapters, even turned off.
Hide the Bluetooth section in that case.\
https://bugzilla.gnome.org/show_bug.cgi?id=749140
The section headings are useful to understand the content
of this panel. Sadly, orca does not currently read them
at all. We can fix this by setting up accessible relations
that help orca figure this out.
https://bugzilla.gnome.org/show_bug.cgi?id=746755
Currently these switches function the opposite of their descriptions.
E.g. the wi-fi switch says "turns off wireless devices" which means that
if the switch is on, wi-fi would go off, but actually the behavior is
the opposite. Reword the labels to be less confusing.
https://bugzilla.gnome.org/show_bug.cgi?id=695417
We were failing to connect to the signal when CanHibernate returned
FALSE; in that case, we would never update the automatic suspend label
when a setting in the dialog was changed.
https://bugzilla.gnome.org/show_bug.cgi?id=733412
This is deprecated in newer automake versions, and this causes warnings
with automake 1.14:
panels/printers/Makefile.am:3: warning: 'INCLUDES' is the old name for
AM_CPPFLAGS' (or '*_CPPFLAGS')
https://bugzilla.gnome.org/show_bug.cgi?id=732189
So that libupower-glib doesn't complain about unset but read
properties, we show the correct icons, and have proper names
for the fake keyboard and mouse.
The DeviceChanged signal was removed, instead, each interesting
device should be monitored individually. This means we need to keep
our own device list locally.
https://bugzilla.gnome.org/show_bug.cgi?id=710393
The upower functionality is deprecated and will return an
error unless upower is built with --enable-deprecated.
The function is also not defined unless the application defines
UPOWER_ENABLE_DEPRECATED, which g-c-c does not do, and the build
system currently does not enable the warning (or error) about this.
https://bugzilla.gnome.org/show_bug.cgi?id=705275
