Bug 539872 – crash in Pitivi Video Editor: I just started the appli...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 539872 - crash in Pitivi Video Editor: I just started the appli...


Summary:	crash in Pitivi Video Editor: I just started the appli...


Status:	RESOLVED DUPLICATE of bug 334631

Product:	pitivi
Classification:	Other
Component:	General
Version:	0.11.1
Hardware:	Other All

Importance:	High critical
Target Milestone:	Git
Assigned To:	Pitivi maintainers
QA Contact:	Pitivi maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-24 02:11 UTC by rgfulford
Modified:	2008-09-04 14:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description rgfulford 2008-06-24 02:11:07 UTC

What were you doing when the application crashed?
I just started the application.


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human-Murrine
Icon Theme: Human

Memory status: size: 106643456 vsize: 106643456 resident: 33714176 share: 18829312 rss: 33714176 rss_rlim: 4294967295
CPU usage: start_time: 1214273426 rtime: 207 utime: 178 stime: 29 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/pitivi'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7e2a8c0 (LWP 5869)]
[New Thread 0xb2f66b90 (LWP 5879)]
[New Thread 0xb378db90 (LWP 5878)]
[New Thread 0xb3f8eb90 (LWP 5877)]
[New Thread 0xb478fb90 (LWP 5876)]
[New Thread 0xb4f90b90 (LWP 5875)]
[New Thread 0xb5992b90 (LWP 5874)]
[New Thread 0xb66e7b90 (LWP 5873)]
(no debugging symbols found)
0xb7fcf410 in __kernel_vsyscall ()

+ Trace 201219

Thread 5 (Thread 0xb478fb90 (LWP 5876))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 XvShmPutImage
from /usr/lib/libXv.so.1
#7 gst_xvimagesink_xvimage_put
at xvimagesink.c line 822
#8 gst_xvimagesink_show_frame
at xvimagesink.c line 2223
#9 gst_base_sink_queue_object_unlocked
at gstbasesink.c line 2137
#10 gst_base_sink_chain_unlocked
at gstbasesink.c line 2548
#11 gst_base_sink_chain
at gstbasesink.c line 2589
#12 gst_pad_chain_unchecked
at gstpad.c line 3523
#13 gst_pad_push
at gstpad.c line 3691
#14 gst_proxy_pad_do_chain
at gstghostpad.c line 193
#15 gst_pad_chain_unchecked
at gstpad.c line 3523
#16 gst_pad_push
at gstpad.c line 3691
#17 gst_proxy_pad_do_chain
at gstghostpad.c line 193
#18 gst_pad_chain_unchecked
at gstpad.c line 3523
#19 gst_pad_push
at gstpad.c line 3691
#20 gst_proxy_pad_do_chain
at gstghostpad.c line 193
#21 gst_pad_chain_unchecked
at gstpad.c line 3523
#22 gst_pad_push
at gstpad.c line 3691
#23 gst_queue_loop
at gstqueue.c line 1021
#24 gst_task_func
at gsttask.c line 192
#25 ??
from /usr/lib/libglib-2.0.so.0
#26 ??
from /usr/lib/libglib-2.0.so.0
#27 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#28 clone
from /lib/tls/i686/cmov/libc.so.6



----------- .xsession-errors ---------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSchrödinger encoder found, using
Bye then!
The program 'pitivi' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 167 error_code 2 request_code 141 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
sys:1: Warning: invalid unclassed pointer in cast to `GstBuffer'
(pitivi:5869): GStreamer-CRITICAL **: gst_mini_object_ref: assertion `GST_IS_MINI_OBJECT (mini_object)' failed
"/usr/bin/pitivi": not in executable format: File format not recognized
--------------------------------------------------

Comment 1 Edward Hervey 2008-09-04 14:57:22 UTC


*** This bug has been marked as a duplicate of 334631 ***