GNOME Bugzilla – Bug 624523
crash in Pitivi Video Editor: Starting pitivi
Last modified: 2010-09-20 08:22:41 UTC
What were you doing when the application crashed? Starting pitivi Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 119758848 vsize: 119758848 resident: 34717696 share: 17719296 rss: 34717696 rss_rlim: 18446744073709551615 CPU usage: start_time: 1279273493 rtime: 55 utime: 49 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/python2.6' [Thread debugging using libthread_db enabled] 0xb782e424 in __kernel_vsyscall ()
+ Trace 222867
Thread 1 (Thread 0xb74cd6c0 (LWP 24783))
A debugging session is active. Inferior 1 [process 24783] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (70591 sec old) --------------------- (evolution:4823): evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' failed (evolution:4823): evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' failed (evolution:4823): evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' failed (evolution:4823): evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' failed (evolution:4823): evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' failed (evolution:4823): evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' failed (evolution:4823): evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
What version of: gstreamer (core) gnonlin gst-python
Here's a copy of the versions of the Debian packages here : ii gstreamer0.10-alsa [gstreame 0.10.29-4 GStreamer plugin for ALSA ii gstreamer0.10-esd [gstreamer 0.10.23-4 GStreamer plugin for ESD ii gstreamer0.10-gnonlin 0.10.15-1 non-linear editing module for GStr ii gstreamer0.10-plugins-bad [g 0.10.19-1 GStreamer plugins from the "bad" s ii gstreamer0.10-plugins-base 0.10.29-4 GStreamer plugins from the "base" ii gstreamer0.10-plugins-good [ 0.10.23-4 GStreamer plugins from the "good" ii gstreamer0.10-plugins-really 0.10.19-0.0 GStreamer plugins from the "bad" s ii gstreamer0.10-pulseaudio [gs 0.10.23-4 GStreamer plugin for PulseAudio ii gstreamer0.10-sdl [gstreamer 0.10.19-1 GStreamer plugin for SDL output ii gstreamer0.10-x [gstreamer0. 0.10.29-4 GStreamer plugins for X11 and Pang ii libgstreamer-plugins-base0.1 0.10.29-4 GStreamer libraries from the "base ii libgstreamer0.10-0 0.10.29-1 Core GStreamer libraries and eleme ii python-gst0.10 0.10.18-2 generic media-playing framework (P ii gstreamer0.10-ffmpeg 0.10.10-1 FFmpeg plugin for GStreamer ii gstreamer0.10-plugins-bad 0.10.19-1 GStreamer plugins from the "bad" s ii gstreamer0.10-plugins-ugly 0.10.15-1 GStreamer plugins from the "ugly" Hope this helps.
Uhmmm... I think I've provided enough info... changing status
Also note that I get this on stdout/stderr at crash time : $ pitivi (pitivi:6671): GStreamer-CRITICAL **: Trying to dispose object "ffmpegcsp0", but it still has a parent "pitivi+elements+mixer+smartvideomixerbin0". You need to let the parent manage the object instead of unreffing the object directly. (pitivi:6671): GStreamer-CRITICAL **: Trying to dispose object "src", but it still has a parent "pitivi+elements+mixer+smartvideomixerbin0". You need to let the parent manage the object instead of unreffing the object directly.
That's most likely a problem with Debian's python-gi. I get the exactly same behaviour if it is installed. Removing it should fix it.
Olivier confirmed in the related Debian bugreport that pitivi works as expected after removing python-gi/pygi.