GNOME Bugzilla – Bug 334631
xvsink crash with python in pitivi
Last modified: 2009-02-04 13:23:57 UTC
When I try to run pitivi, I get an X error crash. If I run pitivi --sync the crash happens when quitting pititiv. Here is the stacktrace:
+ Trace 66952
This is pitivi HEAD, with gstreamer of CVS around the time of February releases.
And here is the error message: Gdk-ERROR **: The program 'pitivi' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 723 error_code 3 request_code 3 minor_code 0) (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.) aborting...
re-assigning to PiTiVi, this is a bad use within the program
behdad, could you try again with latest CVS, the following commit should have fixed the issue. 2006-03-15 Edward Hervey <edward@fluendo.com> * pitivi/pitivi.py: * pitivi/playground.py: Implement shutdown method for properly exiting PiTiVi * pitivi/ui/mainwindow.py: Use instance.PiTiVi.shutdown() when quitting
Still the same.
Created attachment 61285 [details] log file Result of GST_DEBUG=3,python:5 bin/pitivi > log 2>&1
Same with gst stack from HEAD. This is the error message I get on startup running pitivi: [behdad@home ~]$ pitivi Gdk-ERROR **: The program 'pitivi' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 33 error_code 3 request_code 3 minor_code 0) (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.) aborting... Aborted And this is with --sync and close pitivi by clicking on the X in window decoration: [behdad@home ~]$ pitivi --sync /home/behdad/.local/lib/pitivi/python/pitivi/ui/ruler.py:140: DeprecationWarning: integer argument expected, got float for i in range(self.border, allocation.width, self.get_zoom_ratio()): Gdk-ERROR **: The program 'pitivi' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 228 error_code 3 request_code 3 minor_code 0) (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.) aborting... Aborted Closing via File menu doesn't crash.
Created attachment 61290 [details] debug log with head. output of GST_DEBUG=5 .local/bin/pitivi > log 2>&1 with HEAD gstreamer.
Backtrace for the startup crash, with HEAD stuff. This is probably nonsense because it's not --sync'ed.
+ Trace 66956
Created attachment 61292 [details] again Still the same. Attaching the log after a clean rebuild of all modules (gst*, gnonlin, pitivi) as suggested by bilboed.
does it still fail with current head ?
Humm, I had to remove my gstreamer build tree. Feel free to close it, or leave it open and I will eventually retry...
Closing bug until behdad finds the power to try it again :) The new error system should give some info it's really gstreamer related.
I ran into the same problem with 0.10.1 under Gnome 2.15.90 on Gentoo/AMD64. So after seeing this bug I checked out CVS, which still has the same problem. Here's a stacktrace: Starting program: /usr/bin/python /usr/bin/pitivi [Thread debugging using libthread_db enabled] [New Thread 47896172707968 (LWP 9239)] [New Thread 1082132816 (LWP 9273)] [Thread 1082132816 (LWP 9273) exited] [New Thread 1082132816 (LWP 9276)] [Thread 1082132816 (LWP 9276) exited] [New Thread 1082132816 (LWP 9277)] [Thread 1082132816 (LWP 9277) exited] [New Thread 1082132816 (LWP 9290)] Gdk-ERROR **: The program 'pitivi' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 24 error_code 3 request_code 3 minor_code 0) (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.) aborting... Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 47896172707968 (LWP 9239)] 0x00002b8fb2b311fc in IA__g_logv (log_domain=0x2b8fb351c9f3 "Gdk", log_level=<value optimized out>, format=0x2b8fb35391c1 "%s", args1=0x7ffff8ec0fe0) at gmessages.c:493 493 gmessages.c: No such file or directory. in gmessages.c (gdb) thread apply all bt
+ Trace 69769
Thread 1 (Thread 47896172707968 (LWP 9239))
Created attachment 69877 [details] pitivi output Here's the output from pitivi --gst-debug-no-color --gst-debug-level=3 3 was the highest debug level I could use without creating multi-megabyte files. There was no gst debugging output from 1 or 2.
This is still a problem for Ubuntu users in Edgy (the development version) using Pitivi 0.10.1: https://launchpad.net/distros/ubuntu/+source/pitivi/+bug/58626 Is there any suggestion that this is fixed or is it just that the original reporter is no longer complaining? "Closing bug until behdad finds the power to try it again :)" Can we please reopen it? I am happy to run any tests/commands you ask me to.
and it's still happening :(
*** Bug 487457 has been marked as a duplicate of this bug. ***
This works for me in Hardy Beta (PiTiVi v0.11.1)
*** Bug 533180 has been marked as a duplicate of this bug. ***
*** Bug 539872 has been marked as a duplicate of this bug. ***
So... the real issue was writing to a non-existing XID. This is now solved by calling gtk.gdk.display_get_default().sync() before calling self.set_xwindow_id(). If this screws up again... I'm lost as to what is to do. 2008-09-04 Edward Hervey <edward.hervey@collabora.co.uk> * pitivi/ui/viewer.py: Call gtk.gdk.display_get_default().sync() before the initial call to set_xwindow_id(). Fixes #334631 ... hopefully FOR EVER !
Edward Hervey, the bug is still present in version 0.11.1 (Ubuntu Hardy x86_64), but you sayd that it's fixed. You fixed it in next versions?
I forgot to post the error: 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 128 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.)
The bug was fixed in 0.11.2 or 0.11.3 .