Debian Bug report logs - #602784
"** (audacious2:29059): WARNING **: Could not open 'Foo - Foobar', no transport plugin available."

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "A. Costa" <agcosta@gis.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: "** (audacious2:29059): WARNING **: Could not open 'Foo - Foobar', no transport plugin available."

Date: Sun, 7 Nov 2010 22:13:29 -0500

Package: audacious
Version: 2.3-2
Severity: normal


Tonight 'audacious' isn't playing certain '.ogg' files, 
(it still plays most '.ogg' files), and I believe not long ago the same
'.ogg' files used to play in 'audacious'.  The files in question do
play in 'amarok' & 'mplayer'. The terminal errors look like:

    ** (audacious2:29059): WARNING **: Could not open 'Foo - Foobar', no transport plugin available.

    ** (audacious2:29059): WARNING **: Cannot play Foo - Foobar: no decoder found.

...those error messages repeat several times.

The file seems normal:

    % file 'Foo - Foobar.ogg'
    Foo - Foobar.ogg: Ogg data, Vorbis audio, stereo, 44100 Hz, ~112000 bps, created by: Xiph.Org libVorbis I

And 'audacious' can play other '.ogg' files with the same 'file' output.

(Note: 'Foo - Foobar.ogg' is not the actual filename.)

Hope this helps...



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash

Versions of packages audacious depends on:
ii  audacious-plugins             2.3-2+b1   Base plugins for audacious
ii  dbus                          1.2.24-3   simple interprocess messaging syst
ii  dbus-x11                      1.2.24-3   simple interprocess messaging syst
ii  gtk2-engines-pixbuf           2.20.1-2   Pixbuf-based theme for GTK+ 2.x
ii  libatk1.0-0                   1.30.0-1   The ATK accessibility toolkit
ii  libaudclient2                 2.3-2      audacious dbus remote control libr
ii  libaudcore1                   2.3-2      audacious core engine library
ii  libaudid3tag2                 2.3-2      audacious id3 tag manipulation lib
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib
ii  libcairo2                     1.8.10-6   The Cairo 2D vector graphics libra
ii  libdbus-1-3                   1.2.24-3   simple interprocess messaging syst
ii  libdbus-glib-1-2              0.88-2     simple interprocess messaging syst
ii  libfontconfig1                2.8.0-2.1  generic font configuration library
ii  libfreetype6                  2.4.2-2    FreeType 2 font engine, shared lib
ii  libglib2.0-0                  2.24.2-1   The GLib library of C routines
ii  libgtk2.0-0                   2.20.1-2   The GTK+ graphical user interface 
ii  libice6                       2:1.0.6-2  X11 Inter-Client Exchange library
ii  libmcs1                       0.7.1-1    Abstraction library to store confi
ii  libmowgli1                    0.6.1-1    a high performance development fra
ii  libpango1.0-0                 1.28.3-1   Layout and rendering of internatio
ii  libsm6                        2:1.1.1-1  X11 Session Management library

Versions of packages audacious recommends:
ii  unzip                         6.0-4      De-archiver for .zip files

audacious suggests no packages.

-- no debconf information

Message #10 received at 602784@bugs.debian.org (full text, mbox, reply):

From: "A. Costa" <agcosta@gis.net>

To: 602784@bugs.debian.org

Subject: Re: Bug#602784: "** (audacious2:29059): WARNING **: Could not open 'Foo - Foobar', no transport plugin available."

Date: Sun, 7 Nov 2010 22:31:26 -0500

Another detail, the terminal also outputs:

	unix-io: Cannot open /home/alfie/.config/audacious/Foo - Foobar: No such file or directory.

Seems odd that it would look in a '.config' directory for an '.ogg' file.

HTH...

Message #15 received at 602784@bugs.debian.org (full text, mbox, reply):

From: John Lindgren <john.lindgren@tds.net>

To: "A. Costa" <agcosta@gis.net>

Cc: 602784@bugs.debian.org

Subject: Re: audacious: ** WARNING **: Could not open 'Foo - Foobar', no transport plugin available.

Date: Fri, 12 Nov 2010 13:05:25 -0500

[Message part 1 (text/plain, inline)]

> Another detail, the terminal also outputs:
>
> 	unix-io: Cannot open /home/alfie/.config/audacious/Foo - Foobar: No such file or directory.
>
> Seems odd that it would look in a '.config' directory for an '.ogg' file.
>
> HTH...

What is the full path of the file you are trying to play, and how are
you communicating that path to Audacious?

For example:
I have a file named "Offenbach, Jacques - Can-Can.ogg " in the "Music"
subfolder of my home folder.  Hence, the full path to the file is
"/home/john/Music/Offenbach, Jacques - Can-Can.ogg".  To play this file,
I need to tell Audacious where to find it.

Option A:
I can open a terminal window in my home folder.  Then, I go to the
"Music" subfolder:

    $ cd Music

Then, I run:

    $ audacious "Offenbach, Jacques - Can-Can.ogg"

Because I am in the "Music" folder already, I don't need to tell
Audacious any more than the simple file name.

Option B:
I can open a terminal window in any folder in the filesystem.  Then, I run:

    $ audacious "/home/john/Music/Offenbach, Jacques - Can-Can.ogg"

Because I am not in the "Music" folder, I need to include the full path
to the file on the command line.

Which of these two options are you trying to do?

-- John Lindgren

[Message part 2 (text/html, inline)]

Message #22 received at 602784-done@bugs.debian.org (full text, mbox, reply):

From: John Lindgren <john.lindgren@tds.net>

To: 549270-done@bugs.debian.org, 602784-done@bugs.debian.org

Subject: Audacious bugs

Date: Wed, 09 Feb 2011 17:01:04 -0500

#549270 is fixed in current stable version of Audacious (2.3-2).
#602784 has been three months without word from the reporter.

So, closing.

-- John

Message #27 received at 602784@bugs.debian.org (full text, mbox, reply):

From: "A. Costa" <agcosta@gis.net>

To: 602784@bugs.debian.org

Subject: Re: audacious: ** WARNING **: Could not open 'Foo - Foobar', no transport plugin available.

Date: Thu, 10 Feb 2011 14:05:43 -0500

Apologies for my being late in replying (post-bug closing); certain
difficult and necessary family duties took priority.  Appearing as
though to be publicly ignoring a maintainer's useful diagnostic
questions isn't what most bug reporters set out to do.  Onward...

On Fri, 12 Nov 2010 13:05:25 -0500
John Lindgren <john.lindgren@tds.net> wrote:

> What is the full path of the file you are trying to play, and how are
> you communicating that path to Audacious?...

> ...Which of these two options {command line 'pwd' file name
> invocation, or full path} are you trying to do?

After those questions, I couldn't reproduce the bug, except from a
playlist.  Examining the playlist where the song title occurred, it
turned out the playlist was corrupt -- no garbage lines, but the
occasional missing line or two.  Maybe 'audacious' did that, or perhaps
it was some restart or other crash that prevented Linux from
writing a file buffer (with playlist data) to disk in time.  The latter
seems most likely.

Brings up another issue, which is that since users tend to keep
playlist files open a lot, (and modify them a lot), and these files can
get pretty long, then playlist files must tend to be fragile
crash-sensitive things.  (My playlist files become "expensive"
since I tweak 'em a lot.  My method is stick a few thousand or so in
file, randomize, then tweak the random sort as I go, to improve the song
contrasts.  Many dinners have background music.)

Given fragile playlists, some kind of consistency preserving atomic
write would be good, preferably journaled.  Since such a feature would
be generally useful, the best thing might be a special library or utils
to get in between media players and the file system, whenever the
players need to modify a playlist.  Such a hypothetical util could solve
the fragility problem for every media player.

HTH...

Send a report that this bug log contains spam.