Opened 15 years ago
Last modified 13 years ago
#1381 new defect
Input file would not be read if environment variable $HOME is not set.
| Reported by: | Owned by: | reimar | |
|---|---|---|---|
| Priority: | normal | Component: | vo |
| Version: | 1.0rc2 | Severity: | normal |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Reproduced by developer: | no | Analyzed by developer: | no |
Description
Input file would not be read if environment variable $HOME is not set.
I'll use mplayer to dump a set of frames in beginning of the video to later generate a gif thumbnail (used in our CMS).
Command:
mplayer -input file=slave.txt -ao null -vo png video.mpeg
slave.txt content:
pause
seek 0 1
frame_step
seek 20 1
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
frame_step
quit
The problem occurred while the envirement variable $HOME was not set. My slave.txt would not be read, and the command dumps all the frames.
I used strace to debug mplayer. My conclusion after reading the trace was that with the envirement variable $HOME not set, mplayer skipped reading the user specific settings, but also skipped reading the input file.
So I wonder if this is a bug, or a expected behavior? It works evenly with an invalid $HOME path.
