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 147248 - xvimagesink crash when xv doesn't support shm
xvimagesink crash when xv doesn't support shm
Status: VERIFIED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.3
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-07-10 06:11 UTC by Tim Ringenbach
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
small patch that fixes the segfault (1.77 KB, patch)
2004-07-10 06:14 UTC, Tim Ringenbach 		none Details | Review

Description Tim Ringenbach 2004-07-10 06:11:57 UTC 
For some reason, my xv support doesn't seem to support shm, or at least thats
the impression I got from the segfaults I was getting. So I made it not crash.
Except now the window just contains garbage. However I get the same garbage
trying to use sdlvideosink or running xine, so unfortunately I think its a
problem with my video driver *sigh*.
Comment 1 Tim Ringenbach 2004-07-10 06:14:12 UTC 
Created attachment 29396 [details] [review]
small patch that fixes the segfault

This is the patch, that it didn't offer to let me upload when I initally filed
the bug.
It has a couple of comments that could use removing that I forgot to remove,
but its a small patch anyway, and I don't know much about xv so someone ought
to review this :)
Comment 2 Danielle Madeley 2004-07-10 15:16:15 UTC 
Adding the PATCH keyword
Comment 3 Benjamin Otte (Company) 2004-07-15 21:19:41 UTC 
Patch adapted and applied.
I can't test As I don't know a way to disable shm support. Please retest and 
- close if it works.
- change status to ASSIGNED when there's still issues

Thanks.
Comment 4 Christian Fredrik Kalager Schaller 2004-11-25 17:55:49 UTC 
Nothing heard back so assuming the patch fixed it. Closing.