[Desktop] Не запускается vlc из Бранча

[Владимир Гусев]

On Sun, 20 Jan 2008 02:12:32 +0300, Pavlov Konstantin <thresh на altlinux.ru>  
wrote:

> vlc -vvv

[vova на vova ~]$ vlc -vvv
VLC media player 0.8.6d Janus
[00000001] main private debug: checking builtin modules
[00000001] main private debug: checking plugin modules
[00000001] main private debug: loading plugins cache file  
/home/vova/.vlc/cache/plugins-04041e.dat
[00000001] main private debug: recursively browsing `modules'
[00000001] main private debug: recursively browsing `/usr/lib/vlc'
[00000001] main private debug: recursively browsing `plugins'
[00000001] main private debug: module bank initialized, found 239 modules
[00000001] main private debug: opening config file /home/vova/.vlc/vlcrc
[00000001] main private debug: CPU has capabilities 486 586 MMX MMXEXT SSE  
SSE2 FPU
[00000001] main private debug: looking for memcpy module: 3 candidates
[00000001] main private debug: using memcpy module "memcpymmxext"
[00000307] main playlist debug: waiting for thread completion
[00000307] main playlist debug: thread 3081980816 (playlist) created at  
priority 0 (playlist/playlist.c:184)
[00000308] main private debug: waiting for thread completion
[00000308] main private debug: thread 3073592208 (preparser) created at  
priority 0 (playlist/playlist.c:210)
[00000309] main interface debug: looking for interface module: 1 candidate
[00000309] main interface debug: using interface module "hotkeys"
[00000309] main interface debug: thread 3065203600 (interface) created at  
priority 0 (interface/interface.c:231)
[00000311] main interface debug: looking for interface module: 1 candidate
[00000311] main interface debug: using interface module "screensaver"
[00000311] main interface debug: thread 3056814992 (interface) created at  
priority 0 (interface/interface.c:231)
[00000313] main interface debug: looking for interface module: 5 candidates
[00000313] main interface debug: using interface module "wxwidgets"
[00000313] main interface debug: thread 3031194512 (manager) created at  
priority 0 (interface/interface.c:216)
[00000313] wxwidgets interface debug: Using last windows config  
'(-1,0,0,1024,768)(0,90,179,457,82)(6,0,0,-1,150)'
[00000313] wxwidgets interface debug: id=0 p=(90,179) s=(457,82)
[00000313] wxwidgets interface debug: id=6 p=(0,0) s=(-1,150)
The program '.' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 268 error_code 11 request_code 146 minor_code 5)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()  
function.)

[vova на vova public]$ vlc -I rc '1x00 - Pilot (DVDRip, RenTV).avi' -  
работает, все нормально, звук и изображение

[vova на vova public]$ vlc -V x11 '1x00 - Pilot (DVDRip, RenTV).avi'
VLC media player 0.8.6d Janus
The program '.' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 268 error_code 11 request_code 146 minor_code 5)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()  
function.)


[vova на vova public]$ vlc -I glx '1x00 - Pilot (DVDRip, RenTV).avi'
VLC media player 0.8.6d Janus
The program '.' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 268 error_code 11 request_code 146 minor_code 5)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()  
function.)

c glx у меня все в порядке в целом..

-- 
С уважением, Владимир Гусев