| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This update is necessary to add support for recent UCM related changes
in ALSA and PulseAudio.
See https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/10
|
|
|
|
| |
(cherry picked from commit 32d094b38cbdf7554c7f31d5fc8b7ff733111ac5)
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit ff34e9234cea046513a2b568f9a3c9f73114dcaa)
|
| |
|
|
|
|
| |
(cherry picked from commit 30078c5981e8767a98f4a4e5c0ca3cacaee045cb)
|
|
|
|
| |
(cherry picked from commit a9ee7dc34e6fe161a15fba1514c5208bd16a0361)
|
|
|
|
|
|
| |
gnome-control-center/panels/network/net-device-wifi.c:1179:1: warning: no previous prototype for ‘nm_client_on_permission_change’ [-Wmissing-prototypes]
1179 | nm_client_on_permission_change (NetDeviceWifi *self) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
| |
nm_client_on_permission_change() was added in 1.24, so depend
on this version.
Closes: #1120
|
| |
|
| |
|
|
|
|
| |
Implementation borrowed from cc-search-panel-row.c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the ubuntu 20.04, we found a regression on HDMI audio. We plug a
HDMI/DP monitor, the output device is the speaker in the output device
combo box, then we select the HDMI from the combo box, the output
device is switched to HDMI audio successfully, but the configuration
box is empty. This will not happen in the ubuntu 18.04, the profile
will show hdmi-stereo in this situation. So I think this is a
regression.
When problem happens, I could see the errors from log:
Gvc: DEBUG: Matching profile for 'output:analog-stereo' is '(null)'
Gvc: DEBUG: Matching profile for 'output:analog-stereo' is '(null)'
Gvc: DEBUG: Matching profile for 'output:analog-stereo' is '(null)'
Through debugging, I found the cc_profile_combo_box_set_device() is
called too early. In the ubuntu 18.04, this function is called after
pulseaudio changes the active_profile, but in the ubuntu 20.04, it is
called ahead of pulseaudio changes the active_profile.
To fix it, add a signal callback function, after pulseaudio changes
the active_profile, this callback function will be called, then call
cc_profile_combo_box_set_device().
Signed-off-by: Hui Wang <hui.wang@canonical.com>
|
| |
|
| |
|
|
|
|
| |
Fixes #1075
|
|
|
|
| |
Let's use a stable version.
|
|
|
|
|
|
|
|
|
| |
This adds a widget called `CcKeyboardShortcutRow`, sub-classing
`GtkListBoxRow`, to handle a shortcut row. This makes the implementation
a bit tidier, rather than handling it all in `CcKeyboardPanel`, and
allows the widgets that compose the row to be laid out in xml.
This is a prerequisite for moving the shortcuts to a new dialog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit includes all the changes that seem to be necessary for
CcKeyboardItem to be used for dealing with multiple keybindings, without
(yet) changing the user interface to expose this.
The `primary_combo` and `binding` fields of `CcKeyboardItem` are
removed, in favor of the existing `key_combos`. No combination is
"primary", since all of them can now be seen and changed equally.
We treat `CcKeyboardItem.key_combos` as a set, that a combo can be added
to or removed from. Though it continues to be represented as a `GList`,
instead of a `GHashTable`, to preserve ordering.
A lot of the keyboard panel code relied on the assumption that only one
combo can be set for each setting, so this required a variety of
miscellaneous changes.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The test needs fixing, and the release needs to happen again.
|
|
|
|
|
|
|
|
| |
This property gives means for Mutter to determine who is in charge of
display rotation for the built-in panel (us or Mutter). The UI must
reflect this change.
Fixes: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1018
|
|
|
|
| |
So we can track changes on this property.
|
|
|
|
|
| |
This property indicates whether the builtin panel orientation is managed by
an accelerometer, thus shouldn't be managed by the display panel.
|
|
|
|
| |
It will be more convenient than a direct DBus call in future commits.
|
|
|
|
|
|
|
|
| |
This will cover the regular case of pads attached to a tablet, but
also the EKR case where the pad is a separate device logically
grouped with a tablet.
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/415
|
|
|
|
|
|
|
| |
This will be used for pad devices, better than the current way of
comparing name strings coming from libwacom.
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/415
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't need to track them much specifically, as we delegate pad
button mapping UI on GNOME Shell. It is however possible to have
tablets with 0 to N pads (upper bound within sanity = 2), so we
must at least reflect that in the "Map Buttons..." button visibility.
This distinction is most important for the combination of EKR plus
Cintiq 27QHD, as this is a pad-less tablet, for which we wouldn't
usually show the "Map buttons..." action.
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/415
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This puts stylus/pad tracking on 2 separate levels. The CcWacomPanel
will look for styli, and treat them as "device leaders", adding a
CcWacomPage for them.
The CcWacomPage will then track the related pad, and update the
"Map buttons..." action visibility according to it.
This simplifies tablet page creation (eg. have it completed in one
step), and decouples the device grouping logic from CcWacomPanel,
which will be useful in future commits.
|
| |
|
| |
|
| |
|
| |
|
| |
|