Fixing Real Player 11 Problem in 64-bit Fedora

June 8, 2011

List below are some of the Real Player problem I’ve encountered on the web or solved.

Real Player Installation Problem

Please check out my post Install and Playing Real Player in Fedora 15 (Lovelock)

Real Player Problem: Got Audio, No Video! (Solved)

If you encounter such situation where the Real Player plays audio perfectly but there is no video. Use the solution below:

  • First you need to install the gstreamer plugins:
 $sudo yum install gstreamer-plugins-ugly
  • Since Real Player is a 32-bit application playing in 64-bit operating system, you need to install 32-bit libraries:
$sudo yum install gstreamer-plugins-ugly.i686
  • If you still do not have video after installing the plugins. In the Real Player, go to Tools >> Preference >> Hardware and toggle with “Use XVideo”. Usually the video works when the XVideo is NOT CHECKED.

Real Player Problem: Got Video, No Audio!

Personally, I’ve never encountered any problem with audio. However, I’ve learned some solution from the web:

  • Switch ALSA audio driver with OSS driver. You can do this by going to Tools >> Preference >> Hardware
  • Under Tools >> Preference >> Hardware, you can also toggle the setting “Force stereo playback”. In some situation, audio works by un-checking “Force stereo playback”.
  • Another solution is to hack the realplay script, you can get the details from here I wonder if it works on Fedora.

Troubleshooting Real Player Problem

If you have any problem playing real media, you can troubleshoot Real Player problem by running Real Player from the terminal.

cd /opt/real/RealPlayer

Check the error message from the terminal and search the web for solution if you can’t find solution in this post.

Cannot Load GTK Module

While fixing my video problem, I’ve encountered some error messages as shown below. Although I’ve fixed these problems; I found that I could still play rm files perfectly without fixing the problem.

  • Gtk-WARNING **: Unable to locate theme engine in module_path: “clearlooks”,
$sudo yum install gtk2-engines gtk2-engines.i686
  • Gtk-Message **: Failed to load module “pk-gtk-module”
$sudo yum install PackageKit-gtk-module PackageKit-gtk-module.i686
  • Gtk-Message **: Failed to load module “canberra-gtk-module”
$sudo yum install libcanberra-gtk2 libcanberra-gtk3 libcanberra-gtk2.i686

When All Else Failed! Use Mplayer

I found that MPlayer plays rm files quite well, you need to install all the codecs before able to play rm files.



Choosing Between 32-bit or 64-bit Linux Operating System

December 7, 2009

When considering whether to use 32-bit or 64-bit Linux, you should consider the need and the usage of the system. If you have proprietary hardware, the drivers and software are usually written in 32-bit. You would also have less problem with software installation such as Adobe Flash player, Adobe Air and most media player, since most of them were written in 32-bit.

You could still install and use 32-bit software in a 64-bit operating environment. However, you need to download all the 32-bit libraries, wrapper and component for installation and compilation. This will increase your hard disk space since you need to maintain both 32-bit and 64-bit libraries.

You should consider using 64-bit operating system if you need to use a particular software application that requires speed and large amount of memory which is supported in 64-bit Linux. If you have more than 3GB of RAM, you should consider using 64-bit operating system because the 32-bit operating system only recognizes 3GB of RAM.

You could use some 32-bit Linux that addresses more than 3GB of RAM. Such Linux must supports PAE (Physical Addressing Extension), a feature provided by Intel.