[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can't play Ogg files with Noatun/Kaboodle



Paul wrote:
Chris Mattern wrote:

I've been having a problem that started with a Debian upgrade several
months ago:  I can't play Ogg Vorbis files with Noatun or Kaboodle in
my KDE setup.  I can play other audio formats just fine, and I can
play my Ogg files on the command line with ogg123, but not both.
The audio player just sits there with "No File".  In Noatun, if I
bring up the play list, the file is there, but it's flickering, like
it's in some sort of tight loop trying to load it.  I can't delete it
(although I can clear the playlist). As I've got most of my collection
set up to play through JuK in Ogg Vorbis format, this is very
frustrating for me, and I don't seem to have any error messages or
anything to help me solve the problem. I've tried reloading the Noatun
package and all the Ogg Vorbis packages it depends on, but it hasn't
helped.  I'm running Debian testing (sarge), kept up to date with
dselect; last update was on the 7th. noatun is package version 3.3.1-2
libogg0 is version 1.1.0-1. libvorbis0a, libvorisenc2 and
libvorbisfile3 are all 1.0.1-1. I am running on i386. I can give exact
package versions of anything else if needed.  Help!


I'm not sure, but had a similar problem when upgrading to 3.3.2 because some packages weren't working for a while. The only thing we could do was wait a while for the packager to issue the fixes. Now 3.3.2 works fine.

If you don't want to upgrade to 3.3.2, then you could probably go to
snapshot.debian.net and get the older version of kde that you were running months ago, and downgrade to it.

But, I suggest 3.3.2.

Paul


Ah, OK.  Testing, at the moment, actually has KDE at 3.3.2.  Patchlevel
is 3.3.2-1.  Noatun at 3.3.2 is in unstable, and requires KDE at 3.3.2-3,
also in unstable.  This is undoubtedly the KDE patching you're referring to.
However, doing a mass upgrade of KDE by hand makes me somewhat nervous.
The chance of screwing up considerably more than my media play is small,
but not nonexistant.  I think I'll wait for the patch to move into testing.
My main problem was I had no idea what was going on, and no idea what to
do to fix it.  I'm willing to wait for the patch to make it to testing,
as long as I have some assurance that the patch is coming.

--
             Christopher Mattern
             UNIX Engineer, Enterprise Tech. Eng.
             syscjm@gwu.edu
             x4-4999

"Which one you figure tracked us?"
"The ugly one, sir."
"...Could you be more specific?"



Reply to: