[MPlayer-users] Does this seem like an mplayer bug?

[Reimar Döffinger]

On Sun, Aug 25, 2013 at 02:26:43PM +0200, Reimar Döffinger wrote:
> On Mon, Aug 19, 2013 at 08:41:51AM -0400, Tom Horsley wrote:
> > I finally tracked down a mysterious bug this weekend, which turns
> > out to be triggered by mplayer when run with no $DISPLAY like
> > so:
> > 
> > unset DISPLAY
> > mplayer -identify -frames 0 trunc.mpg
> > 
> > My GUI display disappears and is replaced with the contents
> > of the VT1 terminal leftover from before X started. This
> > happened when it opened /dev/fb0 and did some ioctl operations.
> 
> I think that is kind of intended.
> But could you provide a full MPlayer log?
> So I at least know if it's the fbdev, fbdev2 etc.
> Using ATI fglrx drivers I cannot reproduce such an issue with either
> of them, but it might be specific to Intel driver or so.

Also, I suspect that nothing actually went wrong at the point where your
screen went black.
Maybe you could try actually playing a video.
I suspect the real issue happens at the very end, when MPlayer does:
ioctl(fb_tty_fd, KDSETMODE, KD_TEXT)
in order to switch "back" to text mode.
You could try commenting out all of those.
In case this is the cause, I suspect we should actually call KDGETMODE and not
do those ioctls when the mode is already graphics.
Also I wonder, why can MPlayer even do this? /dev/tty should not be
available to ordinary users. Are you running it as root from cron?
That is a really, really, bad idea.