RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
It's useful to know what codec is used for playback/record channels so spice-gtk could print to debug output at channel creation.

Version-Release number of selected component (if applicable):
spice-gtk3-0.33-1.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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 sent
https://lists.freedesktop.org/archives/spice-devel/2017-March/036808.html

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