[FAQ] MP3 support in Fedora Core 2


Recommended Posts

this may sound stupid but when i double click it...it asks what to open it with...i see nothing that would be able to..

You need to become su (in a terminal) and type rpm -ivvh xmms-mp3*.rpm

You could open it with rpm I guess, but then you'd need to be root to install it systemwide.

just use up2date to get mp3 support for this type this into terminal

# up2date xmms-mp3 gstreamer-plugins-mp3 libmad libid3tag

after installing finished do this

One thing you'll need to do is fire up xmms and go to Options -> Preferences then choose Audio I/O Plugins. In that list scroll down and find the MPEG Layer 1/2/3 Placeholder Plugin and disable it. Then enable the new plug-in you just downloaded which is listed as MPEG Layer 1/2/3 Player. Now MP3s should play just fine.

Source: FC 2 Tips

It worked for me :D

^Best solution. You have to add another repository to the yum list first.

From the same page:

Edit /etc/sysconfig/rhn/sources

and add:

yum livna-stable http://rpm.livna.org/fedora/2/i386/yum/stable/

apt fedora-us-stable-fc2 http://download.fedora.us fedora/fedora/2/i386 stable

Then you'll be able to add alot of extra software directly from up2date

Yeah the second one is a pretty big apt repository.

Fedora.US started as a group making extra packages for Red Hat linux products. When Red Hat decided to make a community version, they merged with the Fedora Linux Project and created... Fedora Core!

strange...when i add those to that file...synaptic crashes...i have to restart X. but now i think everything is fine.

but they arent showing up there...how can i add them to synaptic?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
    • One Year In
      slackerzz earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!