Re: "mplayer -vo xvidix" problems with sudo
> > What do you mean? There's only one executable 'mplayer' and only one 'sudo'. > > He means that sudo sets a hard-coded $PATH (defined at compile time) and su > sets a potentially different one derived from any of several places. A similar alternative (to the original question) is that it could be due to the $HOME variable too- mplayer does have config files in your home directory (well, the version I have does, I've not tried the .deb version tho). Well, more accurately, there's a config file that may be empty, and a codecs file that should have *lots* of info in it, and a registry file for windows emulation, to use those windows based codecs (does the .deb have these?). Tomble -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "mplayer -vo xvidix" problems with sudo
On Sat, Jun 01, 2002 at 12:43:49AM -0400, Oleg wrote: > > On Saturday 01 June 2002 12:04 am, Ron Johnson wrote: > > Could it be the difference in $PATH between the 2 commands? > > What do you mean? There's only one executable 'mplayer' and only one 'sudo'. He means that sudo sets a hard-coded $PATH (defined at compile time) and su sets a potentially different one derived from any of several places. -- Marc Wilson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "mplayer -vo xvidix" problems with sudo
On Saturday 01 June 2002 12:04 am, Ron Johnson wrote:
> Could it be the difference in $PATH between the 2 commands?
What do you mean? There's only one executable 'mplayer' and only one 'sudo'.
I also added /usr/bin/id to the list of commands I can run as root, and it
printed "uid=0(root) gid=0(root) groups=0(root)" - same as after `su`. So
just don't see where in theory the difference in behaviour could come from.
Oleg
P.S. Let's exclude the possibility that the program checks for $SUDO_UID and
refuses to run on purpose.
> On Fri, 2002-05-31 at 14:38, Oleg wrote:
> > Hi
> >
> > The only way I can get mplayer to work as well as or better than its
> > Windows counterpart on my hardware is by using "-vo xvidix" option that
> > requires superuser privileges, so I added
> >
> > oleg ALL = (root) NOPASSWD: /usr/local/bin/mplayer *
> >
> > to /etc/sudoers. Now "sudo mplayer -vo xvidix file_name" starts (no
> > permission problems), but fails with these errors:
> >
> > errors when running with sudo
> >
> > No vidix driver name provided, probing available ones!
> > vosub_vidix: Couldn't find working VIDIX driver
> > Error opening/initializing the selected video_out (-vo) device!
> > ---end
> >
> > Surprisingly, however, after doing "su" instead of using sudo, everything
> > works fine (output below). Why the different behaviour with sudo compared
> > to su?
> >
> >
> > Thanks
> > Oleg
> >
> >
> >
> >
> >
> > ---output when running as root -
> >
> > No vidix driver name provided, probing available ones!
> > [genfb] probe
> > Error occured durint open: No such device
> > [mach64] Found chip: 3D Rage Pro AGP 1X
> > [mach64] Video memory = 2Mb
> > [mach64] Planar YUV formats are supported :)
> > vosub_vidix: Using: BES driver for Mach64/3DRage cards by Nick Kurshev
> > and Michael Niedermayer
> > =
> >= Opening Video Decoder: [mpegpes] MPEG 1/2 Video passthrough
> > VDec: vo config request - 220 x 160, Mpeg PES
> > [PP] Sorry, postprocessing is not available
> > Couldn't find matching colorspace - retrying with -vop scale...
> > SwScale: -1 x -1 (-1=no scaling)
> > Sorry, selected video_out device is incompatible with this codec.
> > VDecoder init failed :(
> > Opening Video Decoder: [libmpeg2] MPEG 1/2 Video decoder v2.0
> > libmpeg2: Using MMX for IDCT transform
> > libmpeg2: Using 3DNOW for motion compensation
> > VDec: vo config request - 220 x 160, Planar YV12
> > [PP] Sorry, postprocessing is not available
> > Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
> > VO: [xvidix] 220x160 => 220x164 Planar YV12
> > vo: X11 running at 1024x768 with depth 16 and 16 bits/pixel (":0.0" =>
> > local display)
> > [xvidix] image properties: 220x160 depth: 12
> > vosub_vidix: using 1 buffers
> > [xvidix] window properties: pos: 402x302, size: 220x164
> > Disabling DPMS
> > stat: 1
> > Detected video codec: [mpeg12] drv:1 prio:0 (MPEG 1 or 2)
> > =
> >= AO: [oss] 44100Hz Stereo Signed 16-bit (Little-Endian)
> > ao2: 44100 Hz 2 chans Signed 16-bit (Little-Endian)
> > audio_setup: sample format: Signed 16-bit (Little-Endian) (requested:
> > Signed 16-bit (Little-Endian))
> > audio_setup: using 2 channels (requested: 2)
> > audio_setup: using 44100 Hz samplerate (requested: 44100)
> > audio_setup: frags: 16/16 (4096 bytes/frag) free: 65536
> > Start playing...
> > *** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes
> > [xvidix] window properties: pos: 402x302, size: 220x164
> > *** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes0%
> > *** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes0%
> > A: 2.0 V: 2.1 A-V: -0.095 ct: -0.019 31/ 31 11% 1% 1.4% 0 0 0%
> > *** free_stream() called ***
> > Successfully enabled DPMS
> > vo: uninit ...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "mplayer -vo xvidix" problems with sudo
Could it be the difference in $PATH between the 2 commands?
On Fri, 2002-05-31 at 14:38, Oleg wrote:
> Hi
>
> The only way I can get mplayer to work as well as or better than its Windows
> counterpart on my hardware is by using "-vo xvidix" option that requires
> superuser privileges, so I added
>
> oleg ALL = (root) NOPASSWD: /usr/local/bin/mplayer *
>
> to /etc/sudoers. Now "sudo mplayer -vo xvidix file_name" starts (no
> permission problems), but fails with these errors:
>
> errors when running with sudo
>
> No vidix driver name provided, probing available ones!
> vosub_vidix: Couldn't find working VIDIX driver
> Error opening/initializing the selected video_out (-vo) device!
> ---end
>
> Surprisingly, however, after doing "su" instead of using sudo, everything
> works fine (output below). Why the different behaviour with sudo compared to
> su?
>
>
> Thanks
> Oleg
>
>
>
>
>
> ---output when running as root -
>
> No vidix driver name provided, probing available ones!
> [genfb] probe
> Error occured durint open: No such device
> [mach64] Found chip: 3D Rage Pro AGP 1X
> [mach64] Video memory = 2Mb
> [mach64] Planar YUV formats are supported :)
> vosub_vidix: Using: BES driver for Mach64/3DRage cards by Nick Kurshev and
> Michael Niedermayer
> ==
> Opening Video Decoder: [mpegpes] MPEG 1/2 Video passthrough
> VDec: vo config request - 220 x 160, Mpeg PES
> [PP] Sorry, postprocessing is not available
> Couldn't find matching colorspace - retrying with -vop scale...
> SwScale: -1 x -1 (-1=no scaling)
> Sorry, selected video_out device is incompatible with this codec.
> VDecoder init failed :(
> Opening Video Decoder: [libmpeg2] MPEG 1/2 Video decoder v2.0
> libmpeg2: Using MMX for IDCT transform
> libmpeg2: Using 3DNOW for motion compensation
> VDec: vo config request - 220 x 160, Planar YV12
> [PP] Sorry, postprocessing is not available
> Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
> VO: [xvidix] 220x160 => 220x164 Planar YV12
> vo: X11 running at 1024x768 with depth 16 and 16 bits/pixel (":0.0" => local
> display)
> [xvidix] image properties: 220x160 depth: 12
> vosub_vidix: using 1 buffers
> [xvidix] window properties: pos: 402x302, size: 220x164
> Disabling DPMS
> stat: 1
> Detected video codec: [mpeg12] drv:1 prio:0 (MPEG 1 or 2)
> ==
> AO: [oss] 44100Hz Stereo Signed 16-bit (Little-Endian)
> ao2: 44100 Hz 2 chans Signed 16-bit (Little-Endian)
> audio_setup: sample format: Signed 16-bit (Little-Endian) (requested: Signed
> 16-bit (Little-Endian))
> audio_setup: using 2 channels (requested: 2)
> audio_setup: using 44100 Hz samplerate (requested: 44100)
> audio_setup: frags: 16/16 (4096 bytes/frag) free: 65536
> Start playing...
> *** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes
> [xvidix] window properties: pos: 402x302, size: 220x164
> *** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes0%
> *** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes0%
> A: 2.0 V: 2.1 A-V: -0.095 ct: -0.019 31/ 31 11% 1% 1.4% 0 0 0%
> *** free_stream() called ***
> Successfully enabled DPMS
> vo: uninit ...
--
+-+
| Ron Johnson, Jr.Home: [EMAIL PROTECTED] |
| Jefferson, LA USA http://ronandheather.dhs.org:81 |
| |
| "I have created a government of whirled peas..."|
| Maharishi Mahesh Yogi, 12-May-2002, |
! CNN, Larry King Live |
+-+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"mplayer -vo xvidix" problems with sudo
Hi
The only way I can get mplayer to work as well as or better than its Windows
counterpart on my hardware is by using "-vo xvidix" option that requires
superuser privileges, so I added
oleg ALL = (root) NOPASSWD: /usr/local/bin/mplayer *
to /etc/sudoers. Now "sudo mplayer -vo xvidix file_name" starts (no
permission problems), but fails with these errors:
errors when running with sudo
No vidix driver name provided, probing available ones!
vosub_vidix: Couldn't find working VIDIX driver
Error opening/initializing the selected video_out (-vo) device!
---end
Surprisingly, however, after doing "su" instead of using sudo, everything
works fine (output below). Why the different behaviour with sudo compared to
su?
Thanks
Oleg
---output when running as root -
No vidix driver name provided, probing available ones!
[genfb] probe
Error occured durint open: No such device
[mach64] Found chip: 3D Rage Pro AGP 1X
[mach64] Video memory = 2Mb
[mach64] Planar YUV formats are supported :)
vosub_vidix: Using: BES driver for Mach64/3DRage cards by Nick Kurshev and
Michael Niedermayer
==
Opening Video Decoder: [mpegpes] MPEG 1/2 Video passthrough
VDec: vo config request - 220 x 160, Mpeg PES
[PP] Sorry, postprocessing is not available
Couldn't find matching colorspace - retrying with -vop scale...
SwScale: -1 x -1 (-1=no scaling)
Sorry, selected video_out device is incompatible with this codec.
VDecoder init failed :(
Opening Video Decoder: [libmpeg2] MPEG 1/2 Video decoder v2.0
libmpeg2: Using MMX for IDCT transform
libmpeg2: Using 3DNOW for motion compensation
VDec: vo config request - 220 x 160, Planar YV12
[PP] Sorry, postprocessing is not available
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [xvidix] 220x160 => 220x164 Planar YV12
vo: X11 running at 1024x768 with depth 16 and 16 bits/pixel (":0.0" => local
display)
[xvidix] image properties: 220x160 depth: 12
vosub_vidix: using 1 buffers
[xvidix] window properties: pos: 402x302, size: 220x164
Disabling DPMS
stat: 1
Detected video codec: [mpeg12] drv:1 prio:0 (MPEG 1 or 2)
==
AO: [oss] 44100Hz Stereo Signed 16-bit (Little-Endian)
ao2: 44100 Hz 2 chans Signed 16-bit (Little-Endian)
audio_setup: sample format: Signed 16-bit (Little-Endian) (requested: Signed
16-bit (Little-Endian))
audio_setup: using 2 channels (requested: 2)
audio_setup: using 44100 Hz samplerate (requested: 44100)
audio_setup: frags: 16/16 (4096 bytes/frag) free: 65536
Start playing...
*** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes
[xvidix] window properties: pos: 402x302, size: 220x164
*** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes0%
*** [vo] Allocating mp_image_t, 224x160x12bpp YUV planar, 53760 bytes0%
A: 2.0 V: 2.1 A-V: -0.095 ct: -0.019 31/ 31 11% 1% 1.4% 0 0 0%
*** free_stream() called ***
Successfully enabled DPMS
vo: uninit ...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
