gnome-mplayer cannot open files over smb

[Eemil Lagerspetz]

Binary package hint: gnome-mplayer

gnome-mplayer cannot open files on my passworded smb server any more.
Regular mplayer works fine, since it opens the files from .gvfs, unaware that there is any smb involved.
gnome-mplayer from Intrepid, version 0.7.0 works fine too.
with gnome-mplayer --reallyverbose ~/.gvfs/share-name/video-file.avi I get:

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: gnome-mplayer 0.9.4-1
ProcEnviron:
 LC_CTYPE=fi_FI.UTF-8
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-mplayer
Uname: Linux 2.6.29-ultimate i686

[Eemil Lagerspetz (eemil-lagerspetz)]

Added attachment: mplayer open over smb success log, with mplayer -msglevel all=6

[Cesare Tirabassi (norsetto)]

This looks like a problem with the ages old version of mplayer we have in the repo. Anyhow, I asked upstream to check it out.

[Kevin DeKorte (kdekorte-gmail)]

I guess I need to get my smb server working, and check this out.

[Kevin DeKorte (kdekorte-gmail)]

Next time, please don't alter your log, it makes things a little harder. Anyway I found that problem. It appears that GIO has issues with determining file access permissions on gio shares and so the smb file was being detected as a streaming file. mplayer should have been able to handle this (it does on my machine), but it appears the one on the users machine does not.

Patch is svn change r1263

[Christopher Armstrong (radix)]

Why was this marked as Fixed Committed in Ubuntu? I don't see any indication that it was fixed in any place in Ubuntu. I'm changing it back to In Progress; if it has actually been fixed in Ubuntu, please say in which version.

[Christopher Armstrong (radix)]

actually, I guess I should change it to New instead of In Progress since I don't know if anyone's actively working on it.

Anyway, I'm having the same problem.

[Cesare Tirabassi (norsetto)]

Don't change statuses which are set by devs; when in doubt its always better to ask than make your own guesses.

[Jean-Paul Calderone (exarkun)]

So why was this marked as Fix Committed in Ubuntu? Which version is it fixed in?

[Eemil Lagerspetz (eemil-lagerspetz)]

Fix Committed means it is fixed in the current development version, not released yet as a package. When that happens, it will be "Fix Released". We would need to download the development version from somewhere.

[Jean-Paul Calderone (exarkun)]

> Fix Committed means it is fixed in the current development version, not released yet as a package. When that happens, it will be "Fix Released". We would need to download the development version from somewhere.

The part that confuses me is that this is a bug against the gnome-mplayer component of Ubuntu. If this were a bug against gnome-mplayer upstream, then I would know what "Fix Committed" means - it would be just as you say. But since this is an Ubuntu component, where was the fix committed to? (Answer in the form of a VCS URL preferred) If that's not how it works, then I'm still not sure about the "Fix Committed" status, so any elaboration would be greatly appreciated!

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-mplayer - 0.9.6-1

---------------
gnome-mplayer (0.9.6-1) unstable; urgency=low

  * New upstream release:
    - new media tracker and audio meter
    - new key "use_pulse_flat_volume" to be set if you are using
      Pulse Audio 0.9.15 (see /usr/share/doc/gnome-mplayer/NEWS.Debian.gz
      and /usr/share/doc/gnome-mplayer/changelog.gz for additional info)
    - workaround for opening files on smb shares (LP: #369426)
    - prevent adding an "empty" filename to the playlist (LP: #348864)
    - add new --large_buttons and --always_hide_after_timeout command
      line options to man page
    - update debian/copyright with the newly added upstream source files
    - upstream is now widely using libtool, which is causing rpath and
      dependancies issues. libtool is really not needed for such a simple
      case so it has been patched out in favour of static linking:
      + updated debian/patches/avoid_libtool.patch to patch configure.in
        and Makefile.am instead of directly Makefile.in
      + debian/rules:
        - patch is now applied in the configure target
        - add aclocal/autoconf/automake calls in the configure target
      + debian/control:
        add autoconf and automake as Build-Depends
    - add debian/NEWS
  * Update debian/copyright in line with updated proposal specification
  * Add patch description to avoid_libtool.patch (thanks lintian)
  * Remove deprecated dh_desktop call
  * Use new dh_quilt_patch and dh_quilt_unpatch commands
  * No change bump of Standards-Version to 3.8.1
  * Changed Section to video (and debug for the dbg binary), in line
    with the new sections recently added to the Debian archive
  * Use LDFLAGS=-Wl,--as-needed instead of specifying manually all libraries

 -- Ubuntu Archive Auto-Sync <email address hidden> Mon, 08 Jun 2009 10:59:47 +0100