[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kaffeine] [Bug 351774] --no-xlib" to libvlc_new() error when watching tv
From:       <g9426562 () trbvm ! com>
Date:       2015-09-05 11:23:35
Message-ID: bug-351774-17878-hBK0DKp6uJ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=351774

--- Comment #15 from g9426562@trbvm.com ---
just added a .m2t that won't play in kaffeine-1.3-1-x86_64 (recorded in
kaffeine-1.2.2-4-x86_64).

if I split the file up (using ProjectX:
http://sourceforge.net/projects/project-x/) I can play the .m2v and .ac3 files
in kaffeine-1.3-1-x86_64. Still get the vlc xlib error messages, but, each file
will play. this is the same whether the tv channel uses .ac3 or .mp2.

trying to play the .m2t gives:
../../../include/vlc_xlib.h:46:vlc_xlib_init: Xlib not initialized for threads.
This process is probably using LibVLC incorrectly.
Pass "--no-xlib" to libvlc_new() to fix this.
[00007ffb90000958] vdpau_avcodec generic error: Xlib not initialized for
threads
[00007ffb90000958] vdpau_avcodec generic error: Xlib is required for VDPAU
No accelerated IMDCT transform found
../../../include/vlc_xlib.h:46:vlc_xlib_init: Xlib not initialized for threads.
This process is probably using LibVLC incorrectly.
Pass "--no-xlib" to libvlc_new() to fix this.
[00007ffb80001268] vdpau_display vout display error: Xlib not initialized for
threads
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba4016848] core decoder error: Could not get display date for timestamp
0
[00007ffba40849f8] core decoder error: Could not convert timestamp 0

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]