Bug 3670 - kino destroy linux
Summary: kino destroy linux
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Funda Wang
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 3431
Blocks:
  Show dependency tree / graph
 
Reported: 2011-12-08 18:32 CET by christian fischer
Modified: 2012-04-04 00:31 CEST (History)
1 user (show)

See Also:
Source RPM: ffmpeg
CVE:
Status comment:

Attachments
File from the bug submitter (12.78 KB, application/vnd.oasis.opendocument.text)
2011-12-09 16:53 CET, Kamil Rytarowski 		Details
text (13.05 KB, text/plain)
2011-12-09 17:12 CET, Manuel Hiebel 		Details
rpm -qa from the submitter (30.11 KB, text/plain)
2011-12-09 17:21 CET, Kamil Rytarowski 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Description christian fischer 2011-12-08 18:32:17 CET 
Kino ( v1.3.4) do not work properly under Mageia1:

sometimes i can work some minutes but for example:
- transfer from JVC : sound is good but no picture ;
- mounting :  unable to clic other clip ...
after some anomalies , Linux accept a few seconds  ctrl-alt-del ,
 but after ten  seconds kernel seem destroy ! 
Reset !

My computer :
CM Intel essential , with core2 duo , and graphic Intel â4 Series Chipset Integrated Graphics Controller.( Driver : Intel 810 and later )

test under opensuse 10.4  and kino 1.3.4 in better ( some problems in transfers )
Comment 1 Kamil Rytarowski 2011-12-09 04:33:07 CET 
Hello!
Try to run kino from your terminal and see if there are some errors on the output.

CC: (none) => n54

Comment 2 Kamil Rytarowski 2011-12-09 16:53:31 CET 
Created attachment 1206 [details]
File from the bug submitter
Comment 3 Kamil Rytarowski 2011-12-09 16:54:33 CET 
Please give me your result of "rpm -qa" and attach as a file here.
Comment 4 Kamil Rytarowski 2011-12-09 17:12:32 CET 
If you use the newest ffmpeg - from updates then the bug is obvious.

"This problem is basically an issue converting YUV to RGB using ffmpeg, in order for it to work ffmpeg needs to be recompiled with x264." http://alexsleat.co.uk/2011/01/09/how-to-fix-no-accelerated-colorspace-conversion-found-from-yuv420p-to-bgr24-opencv-2-2-0-ubuntu-10-10/

And the changelog of ffmpeg
* Thu Nov 24 2011 fwang <fwang> 0.7.8-1.1.mga1
+ Revision: 171564
- disable x264 support as x264 is too old in mageia 1
Comment 5 Manuel Hiebel 2011-12-09 17:12:48 CET 
Created attachment 1207 [details]
text
Manuel Hiebel 2011-12-09 17:13:06 CET

Attachment 1206 is obsolete: 0 => 1

Comment 6 Kamil Rytarowski 2011-12-09 17:14:18 CET 
I'm assigning the bug to Funda.

Status: NEW => ASSIGNED
Assignee: bugsquad => fundawang

Manuel Hiebel 2011-12-09 17:20:34 CET

Source RPM: (none) => kino

Comment 7 Kamil Rytarowski 2011-12-09 17:21:20 CET 
Created attachment 1209 [details]
rpm -qa from the submitter
Kamil Rytarowski 2011-12-09 17:21:52 CET

Source RPM: kino => ffmpeg

Comment 8 Kamil Rytarowski 2011-12-09 17:24:31 CET 
So yes, this is the problem with absent x264 for ffmpeg.
Funda Wang 2011-12-10 01:33:51 CET

Depends on: (none) => 3431

Comment 9 christian fischer 2011-12-12 12:58:00 CET 
I uninstall  kino and kdenlive and 2mandvd , and then install ffmpeg « Tainted » , and official Mageia1 kino an kdenlive,

 kino work better.

But Import do not work :  pictures are black, unabled to import :
Comment 10 christian fischer 2011-12-12 13:03:08 CET 
I try to work with Kino on Cauldron .
it work without error, import fron JVC work too, but i cannot export mpeg !
( december 12 2011 )
Comment 11 Kamil Rytarowski 2011-12-12 13:41:32 CET 
Please be patient there were issues with ffmpeg.
Comment 12 Kamil Rytarowski 2012-04-03 15:14:33 CEST 
Ping! Is this bug fixed?
Comment 13 christian fischer 2012-04-03 16:20:22 CEST 
yes 
kino is good on Mageia1.
Comment 14 christian fischer 2012-04-03 16:30:20 CEST 
Y am trying some minutes On Mageia2 (Cauldron) .
 kino seem good.
Comment 15 Manuel Hiebel 2012-04-04 00:31:54 CEST 
so closing

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.