Strange behaviour when starting vlc in xsession script

[d.s.e]

hi,

I'd like to use vlc a s a videoplayer on a mediaserver, controlled by my own application.

to start, I use the following commandline:

vlc -I rc --rc-host 127.0.0.1:4200 --fullscreen --vout xvideo --xvideo-display :0.0 &

when I do this in the x-terminal or from a remote shell, everthing works as expected: I can connect to the port and control vlc, and the screen is blank unitl playback starts.

but when I try to start vlc automatically by inserting this commandline into the .xsession script, vlc shows the standard control interface on the screen instead of allowing a rc connection.

why? what can I do to change this?

[dionoea]

I guess that it's not getting the command line options you gave it. Maybe you need to escape those in xsession scripts ... or something like that.

[d.s.e]

no, all the other commandline options are taken.

I did some tests:
when started within a shellscript, vlc always tries to use the wxwidgets interface, ignoring other settings. this is independent of the user.
even on the same shell, direct start works, start via script not. very strange...

maybe the following log message is interesting:
VLC: main: looking for interface module: 5 candidates
VLC: rc: fd 0 is not a TTY
VLC: main: using interface module "wxwidgets"

[dionoea]

Try adding --rc-fake-tty to your options. (see vlc -p rc --advanced --help-verbose)

[d.s.e]

thanks, that works!

what are the reasons for this behaviour/option?

[dionoea]

Must be a bug in the code. VLC checks if you're in a tty when using the rc interface in a shell. It shouldn't need to do so if you're setting it up to use a tcp connection.