Bug 85622 - compatibility - realplayer 8 for linux hangs during configuration
compatibility - realplayer 8 for linux hangs during configuration
Product: Red Hat Public Beta
Classification: Retired
Component: bash (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Ben Levenson
: 86041 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2003-03-04 23:31 EST by David White
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-05 04:14:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David White 2003-03-04 23:31:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030206

Description of problem:
Downloaded installer from URL, renamed and did the install as root.  Downloaded
codecs for RealVideo 9 and copied the two required codecs into
/usr/lib/RealPlayer8/Codecs.  Made a symlink from /usr/lib/RealPlayer8/realplay
to /usr/local/bin.  As normal user, typed realplay and hit Enter.  Configuration
wizard comes up.  When I get to final screen of configuration wizard (select
connection speed), dialog hangs as soon as I select my speed (384K).  Dialog
unresponsive, need Ctrl-C to kill it.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. See description above.

Actual Results:  Hung dialog.  Unable to use RealPlayer8 for Linux on RC6.

Additional info:

Hopefully, you can provide a workaround?
Comment 1 Tim Waugh 2003-03-05 04:14:03 EST
This is not a bug in bash, or even Red Hat Linux, and this is not a support forum.

However, I happen to know that LD_ASSUME_KERNEL=2.2.5 works around this
realplayer bug.
Comment 2 Mike A. Harris 2003-03-14 18:56:27 EST
*** Bug 86041 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.