Skip to main content

Play MP3s with RHEL 6


Solution:  Install Rhythmbox and the supporting packages.

Issue:  MP3 support is not enabled due to licensing on RHE 6.

I recently reconstructed my laptop host using RHEL 6.3 x86_64.  Things went much more smoothly this time and I have a rather usable desktop environment now ;-)

rhn-channel -v -u rhnuser@example.com -a -c rhel-x86_64-workstation-optional-6 -a -c rhel-x86_64-workstation-supplementary-6
# NOTE: you will most likely need to find out which version of the EPEL noarch.rpm is out there.  6.5 will be out of date.
 rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-5.noarch.rpm
yum -y install yum-plugin-priorities

rpm -Uvh http://download1.rpmfusion.org/free/el/updates/testing/6/x86_64/rpmfusion-free-release-6-0.1.noarch.rpm http://download1.rpmfusion.org/nonfree/el/updates/testing/6/i386/rpmfusion-nonfree-release-6-0.1.noarch.rpm

# MISC (mostly audio-type stuff)
yum -y install id3lib mesa-demos mesa-libGL alsa-plugins-pulseaudio
yum -y install gstreamer-plugins-bad-free gstreamer-plugins-bad-free-extras gstreamer-plugins-base phonon-backend-gstreamer
yum -y install gstreamer*x86_64
yum -y install lame lame-devel lame-mp3x lame-libs
yum -y install esound-devel esound-libs esound-tools libvorbis-devel alsa-plugins-*
yum -y install gstreamer-plugins-ugly gstreamer-ffmpeg two-lame






* * * * * * * * * * * * * * *
ALTERNATE ENDING

* * * * * * * * * * * * * * *
Solution:  Install XMMS and the supporting packages.

Issue:  MP3 support is not enabled due to licensing on RHEL.

While I was researching how to resolve this particular issue I was quite disappointed that I could only find solutions which involved adding 3rd-party repo's to your system.  The only way I want to add an entire repo is if it is Red Hat supported, or... at a minimum.. recognized by Red Hat.  I added Google and Adobe repo's and then the EPEL repo.

Unfortunately this procedure is not inclusive of ALL the necessary steps, because my default built would have included a number of packages (glib2, gtk, etc...).  But, this should get you going.  NOTE: This was done on RHEL 6.2 - the EPEL package will be out-of-date and you will need to browse the directory to figure out what RPM is current.

# rhn-channel -v -u rhnuser@example.com -a -c rhel-x86_64-workstation-optional-6 -a -c rhel-x86_64-workstation-supplementary-6
# rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-5.noarch.rpm

# yum -y install yum-plugin-priorities
# rpm -Uvh http://download1.rpmfusion.org/free/el/updates/testing/6/x86_64/rpmfusion-free-release-6-0.1.noarch.rpm http://download1.rpmfusion.org/nonfree/el/updates/testing/6/i386/rpmfusion-nonfree-release-6-0.1.noarch.rpm


# Enable MP3 playback
yum -y install esound-devel esound-libs esound-tools libvorbis-devel alsa-plugins-*
cd
mkdir XMMS; cd XMMS
wget http://www.xmms.org/files/1.2.x/xmms-1.2.11.tar.gz
wget http://files.softicons.com/download/system-icons/human-o2-icons-by-oliver-scholtz/png/32x32/apps/xmms.png
cp xmms.png /usr/share/icons/hicolor/32x32/apps/
tar -xvzf xmms-1.2.11.tar.gz
cd  xmms-1.2.11
./configure && make && make install

I don't recommend the following... (but I thought I would leave up here, as I did try using rpmforge)

Alternate Solution:  Use the rpmforge repo.
I don't like going this route as it seems to put my system in a position for future issues. So, I add the repo - add my packages and then disable the repo.  Hopefully this will not cause too much turmoil on my box...



# yum -y install yum-priorities
# rpm -ivh http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
# yum -y install gstreamer-plugins-ugly gstreamer-plugins-bad
# mv /etc/yum.repos.d/rpmforge.repo /etc/yum.repos.d/rpmforge.repo.disabled
You should now be able to fire up rhythmbox.

Comments

  1. its working now.... thanks alot buddy......

    ReplyDelete

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you delete a file, it may

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils [root@rh7tst01 ~]# cd /