Bug 1436249
Summary: | Print audio codec used for record/playback channels during channel creation in debug outputs | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | David Jaša <djasa> | |
Component: | spice-gtk | Assignee: | Default Assignee for SPICE Bugs <rh-spice-bugs> | |
Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> | |
Severity: | unspecified | Docs Contact: | Victor Toso <victortoso> | |
Priority: | unspecified | |||
Version: | 7.4 | CC: | djasa, pgrunt, rbalakri, tpelka, victortoso | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | spice-gtk-0.33-4.el7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1436251 (view as bug list) | Environment: | ||
Last Closed: | 2017-08-01 15:06:41 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
David Jaša
2017-03-27 13:54:37 UTC
At channel creation we don't know. We know based on SPICE_MSG_PLAYBACK_MODE message which we print a message (in playback): https://cgit.freedesktop.org/spice/spice-gtk/tree/src/channel-playback.c#n349 I guess it would be more clear to include the mode/codec as string when we recebe the start message (SPICE_MSG_PLAYBACK_START and SPICE_MSG_RECORD_START). Looks good to you? (In reply to Victor Toso from comment #1) > At channel creation we don't know. We know based on SPICE_MSG_PLAYBACK_MODE > message which we print a message (in playback): > > https://cgit.freedesktop.org/spice/spice-gtk/tree/src/channel-playback.c#n349 > > I guess it would be more clear to include the mode/codec as string when we > recebe the start message (SPICE_MSG_PLAYBACK_START and > SPICE_MSG_RECORD_START). > > Looks good to you? Yeah, that would be great. Thanks! Patch pushed 7721d0906d55cfaa6ce8f5786829c5c738adf74c Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1849 |