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.



Fedora Cron and Anacron Schedule Setup

January 24, 2010

This article assumes that you have the basic knowledge of cron and anacron. With the availability of both cron and anacron tools, different Linux distribution configures their schedule task differently.

For Red Hat Linux and Fedora system, there are also significant changes compared to the previous setup.

Before Fedora 10, the default crontab file is setup as follows:

01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly

In the older version of Red Hat Linux and Fedora, anacron was setup to run during the system boot up and initialization process. A script file named as anacron can be found in /etc/rc.d/init.d, the directory that stores the system boot up script.

However, from Fedora 11 onwards, the cron jobs mentioned above are split between cron and anacron.

The default crontab file has no entries as shown below:

# .—————- minute (0 – 59)
# |  .————- hour (0 – 23)
# |  |  .———- day of month (1 – 31)
# |  |  |  .——- month (1 – 12) OR jan,feb,mar,apr …
# |  |  |  |  .—- day of week (0 – 6) (Sunday=0 or 7)  OR
# |  |  |  |  |
# *  *  *  *  *  command to be executed

So, where are the cron jobs’ configurations? First, all the daily, weekly and monthly scripts are configured under anacrontab and it is set to be run by anacron. The default anacrontab file is as follows:

1   65     cron.daily          nice run-parts /etc/cron.daily
7   70     cron.weekly         nice run-parts /etc/cron.weekly
@monthly 75 cron.monthly       nice run-parts /etc/cron.monthly

With anacron running all the scripts located in /etc/cron.daily, cron.weekly and cron.monthly. Cron is left with running the scripts in /etc/cron.hourly. The configuration of the hourly cron job is located at /etc/cron.d/0hourly. The default is as follows:

01 * * * * root run-parts /etc/cron.hourly

Since anacron is not a daemon, this means that anacron need to be activate by scheduled scripts or command. In Fedora, a script file named “0anacron” is located at /etc/cron.hourly. This indicates that anacron is schedule to run on an hourly basis.

In conclusion, the cron daemon in Fedora now only run the script stored in /etc/cron.hourly which configuration is based on /etc/cron.d/0hourly. In the folder /etc/cron.hourly there is a script that runs anacron on an hourly basis. This anacron script then runs all other scripts in the daily, weekly and monthly folders.

Therefore, from Fedora 11 onwards you need to installed cron and anacron in order to have your system task scheduler running properly.

While this is a good arrangement, since most users do not turn on their PC 24×7, I agreed with some users’ suggestion that Fedora should include additional explanatory notes to explain the new configuration in the file crontab.

If you want to remove anacron and use cron exclusively, you need to use the old configuration of crontab and append to the crontab as shown below:

# .—————- minute (0 – 59)
# |  .————- hour (0 – 23)
# |  |  .———- day of month (1 – 31)
# |  |  |  .——- month (1 – 12) OR jan,feb,mar,apr …
# |  |  |  |  .—- day of week (0 – 6) (Sunday=0 or 7)  OR
# |  |  |  |  |
# *  *  *  *  *  command to be executed
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly

It is not advisable to remove cron because anacron cannot run a task at a specific time.


Video Problem with GNOME and X Windows in Fedora installed in VirtualBox

January 16, 2010

This article basically address the problem when X Window won’t start after you have installed VirtualBox Guest Addition in Fedora as Guest OS.

If you are using the latest version of VirtualBox and Fedora 12, you should not have any problem with the drivers. The VBox video drivers works well with HAL in Fedora.

However, there is one exception. After installing VirtualBox Guest Addition on Fedora, you can freely adjust the size of the windows in the VirtualBox. If you happen to adjust VirtualBox windows to maximize the full screen on a 22″ or greater LCD, you will have problem starting X Windows on the next reboot. After maximizing the VirtualBox to the maximum, you would not be able to start X Window (specifically gdm) on the next reboot.


I have a 22″ LCD monitor with default resolution of 1680×1050 in Windows Vista. I have manage to adjust the VirtualBox Window (Fedora 12 as Guest) to 1504×932 without problem restarting Fedora. However, if I maximize the VirtualBox Window to occupy the full screen except Vista status bar (resolution of 1680×957), I would have problem starting X Window on the next reboot.


There are 2 ways to resolve this issue.

The first solution is NOT to maximize the VirtualBox window before restarting Fedora. If you need to maximize the VirtualBox window to work on Fedora, you must remember to reduce the window back to its original size. This is the easiest solution except that you have to remember to reduce the window before restarting Fedora or shutting down Fedora.

If  you prefer to work on the maximize  VirtualBox window size all the time, you can do so that by reverting to the old method of configuring the screen resolution using configuration file. The second solution is to manually configure screen resolution. Please be aware that after configuring the screen resolution, you cannot adjust VirtualBox window freely anymore.

We use xorg.conf configuration file to configure screen resolution. This file is no longer located at /etc/X11 because Fedora is using HAL to manage video and screen resolution. In the older Fedora system, xorg.conf is the main configuration file for video size, dept and resolution.

How to Login when X Windows Fails to Start

When X Windows fails to start, use the key Ctrl+Fn+F2 or Ctrl+Fn+F3 to switch to another virtual windows using console login.

Creating X11 Video Configuration File (xorg.conf)

Since the new Fedora system don’t use xorg.conf anymore. You couldn’t find it in /etc/X11 folder. To generate this file automatically use the command #Xorg -configure. This command creates a file “” after probing the video system. You need to read the output as it indicates where this new file is created.

Then you need to rename the file to xorg.conf and move this configuration file to /etc/X11 folder.

Finally, you need to define the screen resolution in the configuration file.

Amending the Configuration File

Open the file xorg.conf with your favorite editor.

On the section “Screen”, look for subsection “Display” with depth of 24.

Insert a new line indicating the Modes “1680×957”, as follows:

Section “Screen”
Identifier   “Default Screen”
Monitor      “Configured Monitor”
Device      “Configured Video Device”
DefaultDepth    24
SubSection      “Display”
Depth           24
Modes           “1680×957”

The resolution of 1680×957 is the maximize window size excluding the Windows task bar. If you have different screen resolution, please check the most appropriate resolution for your  screen.

Please note that using the xorg.conf will prevents you from adjusting the VirtualBox window dynamically.

If you want to revert to dynamic window adjustment, make sure Fedora is shut down with smaller screen resolution. You can remove the file xorg.conf.


No GNOME Desktop Login Sound after Login to Fedora 12

January 15, 2010

This is a minor problem, but some users might want to listen to a welcome tune after login to Fedora 12.

First, get a copy of desktop login tune (desktop-login.ogg) from Fedora 11. You can also download from here: desktop-login.ogg

Then copy this file to the folder /usr/share/sounds/freedesktop/stereo

Logout and login again, you should be able to hear the login tune after login.

If there is still no desktop login sound,  select: System >> Preference >>Startup Applications

Ensure that the application “GNOME login sound” is check. Click edit and make sure that the command /usr/bin/canberra-gtk-play –id=”desktop-login” –description=”GNOME Login” is available.

Depends on the sound drivers and the sound system initiation procedure, some system may not be able to play the sound.


Fedora 12 Kernel Update Issue

December 23, 2009

This articles is to help users resolve simple problem regarding kernel update. The most common problem is after a kernel update is when the system fails to boot. Occasionally,  problems occurs with the kernel updates, you need to boot to previous kernel until further system update provides patches to the system.

Booting to Previous Kernel

  • When the system startup, press <Tab> few times to make sure the boot menu shows. If it doesn’t work, try a few times.
  • The <Tab> key must hit  the system when the system boots up.
  • IF you manage to get the boot menu, move the arrow key and select the previous kernel release.

Configure Boot Menu to use Previous Kernel

  • Once you are into the system, you need to configure the boot menu such that it boots to the previous kernel.
  • Use your favorite editor and open the  file /boot/grub/grub.conf using root access.
  • In the menu, change the default to 1.

Configure Boot Menu to show Boot Menu

  • To avoid hitting <tab> key many time to display the boot menu, you might want to change some entries in the grub.conf file.
  • Open the file /boot/grub/grub.conf.
  • Under the entry timeout=0, change it to timeout=2. This allows the boot menu to show for 2 seconds.
  • Hash out the #hiddenmenu. This will show the boot menu.
  • Every time when you start the machine, the boot menu will display for 2 seconds.

Drivers Failed after Kernel Update

  • Unfortunately, some driver which you’ve installed manually usually failed after kernel update. There is nothing much you can do except to reinstall all the proprietary drivers after kernel update.
  • The most common driver issue are video drivers and sound drivers.
  • If you’ve install proprietary Nvidia drivers to run Compiz. You need to reinstall the drivers every time when there is a new update on the kernel.
  • If you do not have a sound driver for your sound card and resort to use ALSA generic sound driver. You need to reinstall the drivers.

Install and Using Beesu on Fedora 12

December 16, 2009
A common utility for running GNOME application using root privileges is gksu and gksudo. Currently these 2 applications are under reviewed by Fedora. Therefore, these packages are not available in the Fedora repository. For Fedora user there is an alternative package called Beesu. Beesu is the alternative package to use to open GNOME application such as Nautilus using root privileges.

Installing Beesu

  • Open a terminal window with root access (su-)
  • Use the following command to install Beesu
    • #yum install beesu
    • #yum install nautilus-beesu-manager

Using Beesu

  • To use Beesu to open Nautilus with root access, use the following procedure:
  • Open a terminal window with normal access, use the following command (use either one)
    • #beesu nautilus
    • #beesu nautilus –browser

Configuring Nautilus with Beesu

The above method is workable. However, it is very cumbersome to open a terminal window every time you want to open Nautilus with root access. Using the package Nautilus Beesu Package, we can configure Nautilus by installing some scripts that uses Beesu function. The procedure for installing such scripts is as follows:

Configuring Nautilus with Beesu

  • Open a terminal windows
  • Run the Nautilus Beesu configuration program with the command
  • $nautilus-beesu-manager
  • A Window will pop-up and you have to choose which script to install. At least choose “Open Nautilus here”. It is also recommended to install the script “Open with gEdit”

Using Nautilus with Beesu Script

  • After installation is done, you can open the normal file browser and navigate to any system folder you might need to access with root privileges.
  • Right-click the system folder and select Scripts >> beesu >> Open Nautilus here
  • Another Nautilus window will appear with root privileges.
  • If you want to be able to edit any script file or configuration file freely, install the script “Open with gEdit”.
  • After the installation, point to any script or configuration file you want to modify with root privileges, right-click and select Scripts >> beesu >> Open with gEdit.
  • gEdit will open the selected script file or configuration file with root access. You don’t have to open a new Nautilus window


How to Open Nautilus as Root

December 16, 2009

There are basically 2 ways to open nautilus as root

Using sudo Command

The simple way is to configure current user to use sudo.

The procedure of configuring sudo is as follows:

  1. Open a terminal window with root privileges using the command below:
  2. #su –
  3. After entering password proceed with the following command to open the sudo file
  4. #visudo
  5. This vi utility will check if your entry is correct. Use visudo instead of vi /etc/sudoers
  6. In the sudo file, remove the # from the statement %wheel  ALL=(ALL)       ALL
  7. Next, open the group file using vi as follows:
  8. #vi /etc/group
  9. Under the entry wheel:x:10:root, append the current login name after root as follows:
  10. wheel:x:10:root,username
  11. Save the file. Now the current user can perform sudo command
  • To open Nautilus as root use the command from the terminal without root access,
  • $sudo nautilus
  • or
    • $sudo nautilus --browser.
  • File browser will open with root access.
  • You can perform the above command in the background as follows (use either command):
    • $sudo nautilus &
    • $sudo nautilus --browser &
  • The other way is to install and use the software package Beesu. Check out this post for details: Installing and Using Beesu on Fedora 12