KINO: can't use "open file" menu

(In reply to comment #0)

I was wrong, I can no longer even drag and drop files into kino...

I am trying to use Ubuntu as a base to do video editing. It has been a hard battle.
So far, I have been able to:
- capture with kino (but not re-load the captured files),
- edit and render with cinelerra

I cannot get ffmpeg to convert the rednered file into dvd format; ffmpeg just
stops at the 11th frame...

I am more than willing to help to get Ubuntu to support this application.

Since then, I now use kino on a 32bit chroot, and ffmpeg built myself from cvs;

this workaround is ok, but it would be nice to move kino back to the 64bit envt...

I still believe tha Ubuntu is a very elegant platform!

(In reply to comment #2)
Now running Breezy on AMD64, problem is not the same, can't open files but kino
doesn't crash...
Also, on 64bit cannot capture as quicktime4linux, but this is available on 32bit....

Thanks for your bug report. Does this still happen to you?

(In reply to comment #4)
> Thanks for your bug report. Does this still happen to you?

Yes,it stil fails, but more gracefully, with a popup: Failed to load media file.

On the 32bit chroot it works fine.

In any case, I've given up on using it under 64bit and now use only 'dvgrab' at
the 64bit command line, editing the video in cinelerra that I built myself from
source. You can see my process described on http://gratefulfrog.net; The
description refers to Hoary, but it still applies under Breezy. I am available
for more info and am happy to help!
JH

Does kino say anything, if you start if from the terminal and then open one of
those files? Are those files big? Could you give a link to them?

(In reply to comment #6)
> Does kino say anything, if you start if from the terminal and then open one of
> those files?
This is the terminal output in both 64 and 32 bit envts for a command line file
open; I will post the file in a separate attachment.
Thanks again!

From the 64bit envt, load fails:
$ kino madoogali2005.03.24_05-49-58.mov > kino64.out
> Kino Common being built
> Creating page editor
> Creating Capture Page
> Creating Export Page
> Creating Export1394 Page
> Creating ExportAVI Page
> Creating ExportStills Page
> Creating ExportAudio Page
> Creating ExportMJPEG Page
> Creating ExportPipe Page
/usr/local/share/kino/scripts/exports/ffmpeg_divx.sh
/usr/local/share/kino/scripts/exports/ffmpeg_vcd.sh
/usr/local/share/kino/scripts/exports/ffmpeg_mp3.sh
ffmpeg version CVS, build 3276800, Copyright (c) 2000-2004 Fabrice Bellard
  configuration: --build x86_64-linux-gnu --enable-gpl --enable-pp
--enable-zlib --enable-vorbis --enable-libogg --enable-theora --enable-a52
--enable-dts --enable-dc1394 --enable-libgsm --disable-debug --prefix=/usr
  built on Sep 29 2005 03:18:55, gcc: 4.0.2 20050808 (prerelease) (Ubuntu
4.0.1-4ubuntu8)
/usr/local/share/kino/scripts/exports/rawplay.sh
/usr/local/share/kino/scripts/exports/ffmpeg_dvd.sh
/usr/local/share/kino/scripts/exports/extract_chapters
/usr/local/share/kino/scripts/exports/ffmpeg2theora.sh
/usr/local/share/kino/scripts/exports/mencoder.sh
/usr/local/share/kino/scripts/exports/ffmpeg_dvd_dual.sh
> Creating page trim
> Creating Magick Page
>> Searching /usr/local/lib/kino-gtk2 for plugins
> setting video preview size to 360x270
>> Starting Editor
>> Kino Common newFile
>> Creating undo/redo buffer
>>> Received playlist to store at position 0
>>>> Adding to end

(kino:22634): Gtk-WARNING **: Ignoring the separator setting
KinoCommon::bulkLoad: Failed to load
/home/bob/Desktop/madoogali2005.03.24_05-49-58.mov
>> Kino Common newFile
>>> Received playlist to store at position 0
>>>> Adding to end
Exiting Kino
> Kino Common being destroyed
>> Leaving Editor
>> Left Editor
> Destroying page editor
> Destroying Capture Page
> Destroying Export Page
> Destroying page trim
> Kino Common destroyed

From the 32bit envt, loads perfectly:
$ kino madoogali2005.03.24_05-49-58.mov > kino32.out
> Kino Common being built
> Creating page editor
> Creating Capture Page
> Creating Export Page
> Creating Export1394 Page
> Creating ExportAVI Page
> Creating ExportStills Page
> Creating ExportAudio Page
> Creating ExportMJPEG Page
> Creating ExportPipe Page
/usr/share/kino/scripts/exports/extract_chapters
/usr/share/kino/scripts/exports/ffmpeg_divx.sh
/usr/share/kino/scripts/exports/ffmpeg_vcd.sh
/usr/share/kino/scripts/exports/ffmpeg_mp3.sh
ffmpeg version CVS, build 3276800, Copyright (c) 2000-2004 Fabrice Bellard
  configuration: --build i486-linux-gnu --enable-gpl --enable-pp --enable-zlib
--enable-vorbis --enable-libogg --enable-theora --enable-a52 --enable-dts
--enable-dc1394 --enable-libgsm --disable-debug --prefix=/usr
  built on Sep 29 2005 03:25:16, gcc: 4.0.2 20050808 (prerelease) (Ubuntu
4.0.1-4ubuntu8)
/usr/share/kino/scripts/exports/rawplay.sh
/usr/share/kino/scripts/exports/ffmpeg_dvd.sh
/usr/share...

(In reply to comment #6)
> Does kino say anything, if you start if from the terminal and then open one of
> those files? Are those files big? Could you give a link to them?

I'm sorry to have made an attachment to the wrong bug... I uploaded the video
footage you requested to bug 23820 instead of this one. The attachment id 5125.
It is described in comment #15.

I remain available for more testing and feedback.
Cheers!

It seems to be fixed with the current Dapper version - works nicely on AMD64.

(In reply to comment #9)
> It seems to be fixed with the current Dapper version - works nicely on AMD64.

just tried the new version of kino in breezy, but the problem continues...

There is kino 0.80 in breezy-backports. It's same version as dapper has.

I have re-installed the 0.80 version, which is in fact Kino 0.7.5 according to the about menu.

The problem persists, on my AMD64 breezy (fully up to date).

When I try to use the open file to load, I get the following:

(kino:15322): Gtk-WARNING **: Ignoring the separator setting
>> Leaving Editor
>> Left Editor
>> Starting Editor

Any ideas?

Can somebody please having the crash (I don't on AMD64) please follow the instructions on http://wiki.ubuntu.com/DebuggingProgramCrash to get a backtrace?

Before I try all the work on the debugging instructions, are you sure it will give useful information? Kino doesn't "crash" it just reports an error and continues.

Let me know,
g

The initial description said it 'crashed'. I just tried the 'edgy' version of kino and it works nicely. Who still has the problem?

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.