9b81e0ee45
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> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| build-aux | ||
| data/icons | ||
| docs | ||
| gettext/its | ||
| man | ||
| panels | ||
| po | ||
| search-provider | ||
| shell | ||
| subprojects | ||
| tests | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| COPYING | ||
| gnome-control-center.doap | ||
| meson.build | ||
| meson_options.txt | ||
| NEWS | ||
| README.md | ||
GNOME Settings
GNOME Settings is GNOME's main interface for configuration of various aspects of your desktop.
Contributing
See docs/CONTRIBUTING.md for details on the contribution process, and docs/HACKING.md
for the coding style guidelines.
Reporting Bugs
Before reporting any bugs or opening feature requests, read the communication guidelines.
Bugs should be reported to the GNOME bug tracking system under the product gnome-control-center. It is available at GitLab Issues.
In the report please include the following information:
- Operating system and version
- For Linux, version of the C library
- Exact error message
- Steps to reproduce the bug
- If the bug is a visual defect, attach a screenshot
- If the bug is a crash, attach a backtrace if possible [see below]
How to get a backtrace
If the crash is reproducible, follow the steps to obtain a backtrace:
Install debug symbols for gnome-control-center.
Run the program in gdb [the GNU debugger] or any other debugger.
gdb gnome-control-center
Start the program.
(gdb) run
Reproduce the crash and when the program exits to (gdb) prompt, get the backtrace.
(gdb) bt full
Once you have the backtrace, copy and paste it into the 'Comments' field or attach it as a file to the bug report.
Testing Unstable Settings
It is quite easy to test and give feedback about the development version of GNOME Settings. Just access https://gitlab.gnome.org/GNOME/gnome-control-center/environments, get the latest version, download it, double-click the file, install and run.
Note that GNOME Settings Flatpak will only work if you are running the latest GNOME version in your host system.