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 377117 - [SEGFAULT] X error : BadWindow
[SEGFAULT] X error : BadWindow
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: General
Git
Other All
: Normal critical
: 0.10.2
Assigned To: Pitivi maintainers
Pitivi maintainers
: 390706 418360 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-19 19:43 UTC by Joel Martins
Modified: 2007-03-20 09:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joel Martins 2006-11-19 19:43:55 UTC
Please describe the problem:
beforehand i should tell you i'm very new at this. 

Ok, now..i started the aplication. 

bunny@bunny-desktop:~$ pitivi
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.)

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
yes, except when i go on pitivi --sync, but i guess thats normal.

Other information:
CPU: Athlon64 3200+
RAM: 1024MB
Main Hardrive: Seagate 160gb 
Secondary Hardrive: Seagate 60gb
Motherboard: Asrock 939NF4G-SATA2  
Chipset: nVidia Geforce 6100
Audio: Realtek ALC850

using Ubuntu 6.1 (Edgy) i386
Comment 1 André Klapper 2006-11-20 10:14:07 UTC
did you install any ubuntu updates before this happened? :-)

(not a blocker by definition.)
Comment 2 Joel Martins 2006-11-21 17:25:11 UTC
Ah yeah, sorry about that! 

Well, i updated everything Ubuntu told me to, i think. I remember a popup showing up when i first installed and i just said yes to all. Didn't see anything against it. I like updating stuff. 

Comment 3 Joel Martins 2006-11-28 16:43:27 UTC
If there's any further or more specified info that you'd like and that i can deliver, just ask. 
Comment 4 Edward Hervey 2006-11-28 16:46:18 UTC
The issue seems to be because the XID is set too early on the video sink. Sinks implementing the GstXOverlay interface emit a GST_MESSAGE_ELEMENT 'prepare-xwindow-id' at which point the application knows it's safe to give it an XID.

Changing title accordingly.

Comment 5 Edward Hervey 2006-11-28 18:02:36 UTC
2006-11-28  Edward Hervey  <edward@fluendo.com>

	* pitivi/playground.py:
	Added new signal 'element-message' to receive gst.MESSAGE_ELEMENT
	messages. This is done synchronously (unlike the other messages
	which are received asynchronously).
	* pitivi/ui/viewer.py:
	Wait for the video sink to request us to give it a XID before setting
	one, this avoids crashes because of setting an XID on something not
	created yet.
	Fixes #377117
	
Comment 6 Edward Hervey 2006-12-29 16:54:03 UTC
*** Bug 390706 has been marked as a duplicate of this bug. ***
Comment 7 Edward Hervey 2007-02-03 11:53:48 UTC
Re-opening bug, since it seems other issues are also causing this crash.
Comment 8 Edward Hervey 2007-03-20 09:42:34 UTC
Ok, this was the previous issue (BadWindow). That one is definitely fixed. Closing again.
Comment 9 Edward Hervey 2007-03-20 09:43:36 UTC
*** Bug 418360 has been marked as a duplicate of this bug. ***