Bug 607710

Summary: [RFE] Please build rdesktop --with-sound=libao
Product: Red Hat Enterprise Linux 6 Reporter: Harald Milz <harald.milz>
Component: rdesktopAssignee: Søren Sandmann Pedersen <sandmann>
Status: CLOSED CURRENTRELEASE QA Contact: desktop-bugs <desktop-bugs>
Severity: high Docs Contact:
Priority: low    
Version: 6.0CC: cmeadors, kem, mail, notting, snagar, vbenes
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rdesktop-1.6.0-8.el6 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:28:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Harald Milz 2010-06-24 15:53:02 UTC
Description of problem:

rdesktop in RHEL 5.x and RHEL6 is not build against the sound libs. Please build rdesktop --with-sound=libao so that ESD and Pulseaudio can work with it. This is critical for an ongoing large customer Linux migration project (80,000+ seats) that integrates legacy Windows terminal servers.

Comment 2 RHEL Program Management 2010-06-24 16:17:20 UTC
This feature request did not get resolved in time for Feature Freeze
for the current Red Hat Enterprise Linux release and has now been
denied. It has been proposed for the next Red Hat Enterprise Linux
release. If you would still like it considered for the current
release as an exception, please make that request with your support
representative.

Comment 3 Felix Möller 2010-06-27 12:08:48 UTC
Strange that this five minute fix cannot get resolved.

There is a duplicate at bug #577878 and bug #457184 and bug #548617 sadly there seems to be nobody careing about rdesktop.

Comment 5 Vladimir Benes 2010-09-14 11:30:15 UTC
compiled with --with-sound=libao flag now
-> VERIFIED

Comment 6 releng-rhel@redhat.com 2010-11-10 21:28:18 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.