[Kdenlive-devel] Another commit and time to start mentioning piave bugs ;-)

[Rolf Dubitzky]

On Monday 10 February 2003 10:59 pm, Jason Wood wrote:
> On Monday 10 Feb 2003 10:21 am, Rolf Dubitzky wrote:
> Erm, that sounds bad :-( On my computer, kdenlive has not crashed or frozen
> since we released V0.2.0, which makes it difficult for me to track down
> what is wrong.

Might it be a KDE 3.1 / 3.0 issue ?

> > b)  insert the clip to the timeline ...
> >       this doesn't work at all for me right now. when I try to d'n'd a
> > clip from the project list to the timeline, the clip doesn't 'drop' i.e.
> > the small square that is displayed next to the mouse coursor just stays
> > where it is and nothing else happens. no clip in the timeline.
>
> This happens when the "duration" of a clip is "unknown". The exact handling
> of this situation needs to be sorted out but this suggests that the
> Document piave instance is not replying to getCapabilities correctly, or if
> it is, then Kdenlive is not picking up the request. I recieve this when I
> try to add clips to the project : (from the Document piave instance, port
> 6100).

Yes, that is the case. I didn't notice it before, but the duration is really 
zero. And that is no surprize, since piave doesn't see a <getFileProp..> 
request.... I'll try to find out where the <getFileProp..> cmnd gets lost...

> server.cc:239 INFO: <message><getFileProperties
> filename="/home/uchian/video/casualty.dv" />

the point is, that for me, I don't even see <getFileProperties> anywhere...

> As already mentioned, the d'n'd not working is due to the "unknown" status
> of a file when it is first dragged into kdenlive - I am considering how
> best to fix this. My initial thought is to have a "mystery" clip type
> (marked with question marks) which resolves itself to the correct clip
> length as soon as it becomes known. However, this get's tricky since piave
> might say that the file is invalid, or not return an answer at all if
> something goes seriously wrong.

I think you should just mark those clips as "un-d'n'd-able" somehow. The 
chance that the duration gets known is small, that chance that it is a bug is 
big. A warning "Couldn't get file properties" wouldn't hurt either, no?

> freeze

Here is a bt for a froze kdenlive. looks like network trouble.. maybe waiting 
for a piave reply that doesn't come.

Starting program: /scratch/users/dubitzky/bin/kdenlive
[New Thread 1024 (LWP 16900)]

Program received signal SIGINT, Interrupt.
[Switching to Thread 1024 (LWP 16900)]
0x4102141e in select () from /lib/libc.so.6
(gdb) where
#0  0x4102141e in select () from /lib/libc.so.6
#1  0x40dd3634 in __DTOR_END__ () from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#2  0x4094a4bc in enter_loop__12QApplication () from 
/usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#3  0x40145b8f in enter_loop__Q23KIO9NetAccess () from 
/usr/lib/libkio-gcc2.96.so.4
#4  0x4014598f in statInternal__Q23KIO9NetAccessRC4KURL () from 
/usr/lib/libkio-gcc2.96.so.4
#5  0x40144e73 in exists__Q23KIO9NetAccessRC4KURL () from 
/usr/lib/libkio-gcc2.96.so.4
#6  0x08063e0b in launchProcess__7KRender ()
#7  0x08062fcb in timerEvent__7KRenderP11QTimerEvent ()
#8  0x409a733b in event__7QObjectP6QEvent () from 
/usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#9  0x40948ff3 in internalNotify__12QApplicationP7QObjectP6QEvent () from 
/usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#10 0x40948e8c in notify__12QApplicationP7QObjectP6QEvent () from 
/usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#11 0x405bbf1b in notify__12KApplicationP7QObjectP6QEvent () from 
/usr/lib/libkdecore-gcc2.96.so.4
#12 0x408f0339 in qt_activate_timers__Fv () from 
/usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#13 0x408edec4 in processNextEvent__12QApplicationb () from 
/usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#14 0x4094a4bc in enter_loop__12QApplication () from 
/usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#15 0x40145b8f in enter_loop__Q23KIO9NetAccess () from 
[...cut...]


> Again, this doesn't happen for me :-( Could you provide a backtrace?

No, because whe I run kdenlive in valgrind or gdb it _always_ freezes. 


QSocket::writeBlock: Socket is not open
QSocket::writeBlock: Socket is not open
QSocket::writeBlock: Socket is not open
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kdenlive path = <unknown> pid = 17039
Alarm clock


Cheers,
Rolf

***************************************************************
 Rolf Dubitzky  
 e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de
 s-mail see http://hep.phy.tu-dresden.de/~dubitzky/
***************************************************************