For GNOME 3.32 we are pushing to make all our avatar images
round. This commit adjusts the existing stock faces images
to avoid layout issues when they are cropped in this way.
Fixes#289
Collect all the parent of a given device and pass that to the device
dialog, so we can show and potentially authorize/enroll all the
parent devices too.
Add an expander that contains a list of all the parent devices of
the dialog's target device. If any of the devices is not yet
authorized, show a warning symbol next to it.
Additionally the enroll/authorize function calls are replaced
by a single bolt_client_connect_all call, so parents that need
authorization can be authorized/enrolled too.
The CcBoltDeviceEntry can now optionally show a warning indicator
if the device is in the pending state.
Since we *don't* want to show this in the main list, remove calls
to gtk_widget_show_all and replace them with gtk_widget_show.
Adds a utility function that deterministically generates an object
path from a path base and an object id.
The corresponding bolt commit is:
a396eb986611ed73fc0ccca2127f29ab1e3aac62
Import five commits that add methods to enroll and authorize multiple
devices at once; meant for authorizing a target device and all the
parents that need to be authorized.
Commits in bolt are:
1ae5c8611fc21c21c8c63ba6933b63eb4c20ab87
d993ca2f871e7e412b4e1f885b24e4f6622dfc55
2689e5f77496ac7698744e582feb9afa3e55e0ac
87762ce14650263ef35f97da5a3a5d122ac0b7d7
5aa5548d6c7fa1fa26733ecd073097bc1b9d31fb
00b3d8a35835b8c856e5de026a0c8316b2ceba90
It is almost surreal to believe that there's a leak in
libasan, but this is blocking CI and it's not something
we can work on right now.
Suppress this leak.
Listen for security level changes, which in theory should not really
happen at all with the exception that on hardware where force power
is not support and boltd has not yet seen the thunderbolt controller
because it was powered down. Then we should get an initial change
from 'unknown' to the real level. Handle it in the same way that
as if boltd was restarted, i.e. the dbus name owner changed
If bolt cannot determine the security level, which in theory should
never happen[1] the standard no-thunderbolt message seems not
entirely appropriate. Instead show a different message that is more
tailored to this unusual case.
[1] The following (unlikely) reasons would invoke such a scenario:
- new security level not supported by boltd
- old hardware with not force-power support and the thunderbolt
controller has not yet been powered up
This will allow the panel to reach smaller sizes.
This deliberately doesn't adapt the indentation of the contained widget
to help this commit to be more readable and easier to review, it will be
adapted in the next commit.
