We were facing this CI build failure error
[573/879] Linking target panels/online-accounts/gnome-control-center-goa-helper
FAILED: panels/online-accounts/gnome-control-center-goa-helper
cc -o panels/online-accounts/gnome-control-center-goa-helper panels/online-accounts/gnome-control-center-goa-helper.p/gnome-control-center-goa-helper.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--start-group /usr/lib64/libgoa-backend-1.0.so /usr/lib64/libgoa-1.0.so /usr/lib64/libgtk-3.so /usr/lib64/libgdk-3.so /usr/lib64/libz.so /usr/lib64/libatk-1.0.so /usr/lib64/libpangocairo-1.0.so /usr/lib64/libharfbuzz.so /usr/lib64/libgio-2.0.so /usr/lib64/libgdk_pixbuf-2.0.so /usr/lib64/libcairo-gobject.so /usr/lib64/libpango-1.0.so /usr/lib64/libcairo.so /usr/lib64/libglib-2.0.so /usr/lib64/libgobject-2.0.so -Wl,--end-group
/usr/bin/ld: /usr/lib64/libtracker-sparql-3.0.so.0: undefined reference to `g_assertion_message_cmpint'
collect2: error: ld returned 1 exit status
g_assertion_message_cmpint is available in newer glib than what's in
our container image.
The method gtk_widget_translate_coordinates is deprecated in gtk 4.12.
Use a new method gtk_widget_compute_point instead.
general: Apply suggestions graphene point
The homogeneous on their boxes has no visible effect, as
the buttons lack hexpand. It, however, still influences
the box's minimal width unnecessarily. Thus, removing it
decreases the panel's minimal and natural width without a
visible change otherwise.
Making those buttons can-shrink also decreases their and
henceforth the panel's minimal width. With this change,
the panel can shrink to a width of 360px, with a natural
width not far from it.
Signed-off-by: Markus Göllnitz <camelcasenick@bewares.it>
We currently load the last-panel every time gnome-control-center
is launched, we do it from the CcWindow contructor method.
But we shouldn't do it when we are explicitly opening a different
panel by eg. using commandline parameter (gnome-control-center keyboard)
or from a DBus method, because otherwise we slow things down by
unnecesarily start launching last-panel just to be cancelled
moments later when the code starts processing the other panel.
We fix it by moving the code that loads last-panel to an idle
handler, so by the time it gets executed the other panel has
already started loading, and we can check for that with the
cc_panel_list_get_current_panel() function we add in this patch.
With this patch, I can feel that panels opened from a
gnome-shell search are presented faster.
Fixes issue #2569
The copy button now generates a system information report with all the system information.
The information is generated by calling the same methods used when populating the System Information window.
get_gnome_version() relies on shell_proxy_ready() to provide it with shell proxy.
This means that we cant call get_gnome_version() without providing proxy as an argument which is fine normally but becomes tedious if we want to call this function multiple times in different scopes.
Fix this by creating the shell proxy inside get_gnome_version() function instead.
Since we're no longer processing the list of graphics devices inside of get_renderer_from_switcheroo, there's no need for this function
as the the list now gets passed around to a different function and automatically freed once it goes out of scope.
Default and non default GPUs were associated with a weight of 1 and -1 respectively which meant default gpus were treated
as a "bigger" entity than non default ones. It meant that when sorting a list of GpuData, the default gpu would end up
at the end of the list since it was treated as the biggest. The resultant list after sorting would end up something like
our pointer
|
|
<gpu>, <gpu>, <gpu>, <gpu>, <default gpu>
With this change the weights of these gpus have been exchanged, making the default gpu to be treated as "smaller" this
changing the order of the sorted list into something like
our pointer
|
|
<default gpu>, <gpu>, <gpu>, <gpu>, <gpu>
This is pretty useful because when creating the gpu information row entries in create_graphics_rows, the default gpu is processed first so it becomes the first element added to the gpu entry list which is how we would expect it to be.
This change brings it more inline with the mockup and it makes sense to not have a number for the default graphics device as that
s always going to be the first device.
