Fails to start with some non-orthodox mplayer customizations

[GoogleCodeExporter]

Hello!

I've filed a bug report against Debian package gnome-mplayer, but
unfortunately, maintainer comments are unhelpful:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536008

What steps will reproduce the problem?

1) I use some non-orthodox mplayer settings (I often use pure mplayer, and
I like the effect of these options on pure mplayer):
pent@neo:~$ cat .mplayer/config
[default]
# Write your default config options here!

fixed-vo=yes
idle=yes

2) mplayer has no problem with these settings:
pent@neo:~$ mplayer
MPlayer dev-SVN-r29358 (C) 2000-2007 MPlayer TeamCan't open joystick device
/dev/input/js0: No such file or directory
Can't init input joystick
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

3) but gnome-mplayer doesn't work:
pent@neo:~$ gnome-mplayer
(nothing happens)

I expect to see gnome-mplayer window, but it never appears.

It looks like fixed-vo=yes and idle=yes customizations are not compatible
with gnome-mplayer. In this case, gnome-mplayer should always invoke
mplayer with -nofixed-vo -noidle options.  

I've looked through the sources, and it looks like mplayer may be invoked
from different places. I've also found that there is EXTRAOPTS option, but
I fail to see where it is actually used. Anyway, it may be problematic to
configure this option, as gnome-mplayer may not start without it at all :-(

I think it's Ok just to use -nofixed-vo -noidle everywhere, unconditionally.

I'm ready to provide any additional info,
Andrey Paramonov

Original issue reported on code.google.com by cmr.P...@gmail.com on 7 Jul 2009 at 6:03

[GoogleCodeExporter]

please run "gnome-mplayer -v" and post the output. mplayer is not even started 
until
you load a file, so I don't think mplayer is involved.

Original comment by kdeko...@gmail.com on 7 Jul 2009 at 7:26

[GoogleCodeExporter]

However, it appears that the idle option is the problem here... It should not 
be used
with gnome-mplayer.

However, I have worked around this issue in SVN.

Original comment by kdeko...@gmail.com on 7 Jul 2009 at 7:34

• Changed state: Fixed