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 110597 - xvideosink crashes metacity
xvideosink crashes metacity
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.5.x
Other Linux
: High major
: ---
Assigned To: Metacity maintainers list
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-04-11 23:48 UTC by David Schleef
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Initialize size_hints at window creation time (15.65 KB, patch)
2003-04-26 17:10 UTC, Keith Packard 		none Details | Review

Description David Schleef 2003-04-11 23:48:34 UTC 
gst-launch videotestsrc ! xvideosink

causes metacity to crash, and exits my X session.  This happens with both
0.6.0 and HEAD.

fvwm2 and twm do not crash.

gst-player with 0.6.0 does not cause metacity to crash, probably because
the xvideosink window is embedded.
Comment 1 Benjamin Otte (Company) 2003-04-12 00:06:18 UTC 
What metacity version?
stacktrace?

Metacity 2.4.34 with cvs HEAD and Metacity 2.4.13 with 0.6.0 didn't
cause problems here
Comment 2 David Schleef 2003-04-12 00:14:36 UTC 
metacity 2.5.0
XFree86 4.2.1 using mga driver (Matrox Graphics, Inc. MGA G550 AGP)

+ Trace 35868

  • #0 kill
    from /lib/libc.so.6
  • #1 pthread_kill
    from /lib/libpthread.so.0
  • #2 raise
    from /lib/libpthread.so.0
  • #3 abort
    from /lib/libc.so.6
  • #4 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #5 g_log
    from /usr/lib/libglib-2.0.so.0
  • #6 meta_bell_notify_frame_destroy
  • #7 meta_bell_notify_frame_destroy
  • #8 meta_window_constrain
  • #9 meta_window_activate
  • #10 meta_window_new
  • #11 meta_display_get_current_time
  • #12 meta_ui_get_display
  • #13 gdk_event_get_graphics_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #14 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 main
  • #22 __libc_start_main
    from /lib/libc.so.6 






Comment 3


Benjamin Otte (Company)





          2003-04-12 11:55:28 UTC
        



Since meta_bell_notify_frame_destroy is a function that is new to
metacity 2.5.0, I tend to believe it's a metacity bug.

So I'm moving it there.






Comment 4


Keith Packard





          2003-04-26 17:06:55 UTC
        



This may be caused by metacity not working correctly when the normal
hints aren't set by the application.  I'll attach a patch which shares
the existing normal_hints manipulation code between the property
reload function and the window creation function.






Comment 5


Keith Packard





          2003-04-26 17:10:06 UTC
        



Created attachment 16029 [details] [review]
Initialize size_hints at window creation time






Comment 6


Elijah Newren





          2003-05-06 20:40:05 UTC
        



Adding PATCH keyword and setting priority->high because of the patch.






Comment 7


Kjartan Maraas





          2003-05-11 15:20:36 UTC
        



Is this patch relevant for 2.2.x too?






Comment 8


David Schleef





          2003-05-12 18:08:14 UTC
        



The bug does not exist in metacity-2.4.34.  I'm not sure which version
ships with Gnome-2.2.






Comment 9


Havoc Pennington





          2003-05-16 23:26:06 UTC
        



Did Keith's patch fix this?







Comment 10


David Schleef





          2003-05-16 23:54:13 UTC
        



It does not crash with 2.5.1, which appears to have the patch.