Red Hat Bugzilla – Bug 440488
Program crash on start up... possible race condition.
Last modified: 2009-01-07 04:13:46 EST
Description of problem: pitivi frequently crashes on startup...but not every time. If I run it under strace, it will not crash. This suggests a race condition somewhere, god only knows where exactly. Other gst based programs like totem aren't crashing for me when opening. Version-Release number of selected component (if applicable): pitivi-0.11.1-2.fc9 How reproducible: ~ 50% of the time on my laptop Steps to Reproduce: 1. open pitivi in a terminal 2. watch for the gui to crash before it completely draws (~50% of the time) 3. terminal error message produced when crash occurs: sys:1: Warning: invalid unclassed pointer in cast to `GstBuffer' (pitivi:4536): GStreamer-CRITICAL **: gst_mini_object_ref: assertion `GST_IS_MINI_OBJECT (mini_object)' failed 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 156 error_code 2 request_code 140 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.)
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I can confirm the bug under Fedora 9 (i386): 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 95 error_code 2 request_code 140 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.)
pitivi-0.11.1.4-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/pitivi-0.11.1.4-1.fc9
pitivi-0.11.2-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/pitivi-0.11.2-1.fc9
pitivi-0.11.1.4-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pitivi'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-8809
pitivi-0.11.2-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
pitivi-0.11.2.2-2.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/pitivi-0.11.2.2-2.fc9
pitivi-0.11.3-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/pitivi-0.11.3-1.fc9
pitivi-0.11.3-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.