Bug 1436251

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	Assignee:	Jonathon Jongsma <jjongsma>
Status:	CLOSED ERRATA	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.4	CC:	cfergeau, fziglio, jjongsma, mtessun, rbalakri, rh-spice-bugs, spice-qe-bugs, tpelka, victortoso
Target Milestone:	rc
Target Release:	7.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spice-0.13.90-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1436249	Environment:
Last Closed:	2018-04-10 13:52:38 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:56:53 UTC

+++ This bug was initially created as a clone of Bug #1436249 +++

Description of problem:
It's useful to know what sound codec is used for playback/record channels so spice-server could print to debug output at channel creation (Opus/Celt051/none). The message is once per channel lifetime so the log level for this message can be pretty low.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jonathon Jongsma 2017-04-13 20:41:52 UTC

Patch accepted upstream as ac6e7a4ebd6ab2d940389398c1750e8660b15f0c

Comment 2 Victor Toso 2017-05-30 13:14:00 UTC

We missed the build for this one. Does not seem important enough for exception.
Moving to 7.5 and keeping the POST

Comment 3 Christophe Fergeau 2017-09-22 09:18:42 UTC

Fixed upstream in v0.13.90~56 so was part of the rebase.

Comment 8 errata-xmlrpc 2018-04-10 13:52:38 UTC

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-2018:0802