Bug 205858 - Totem crashes if you resize the window when using ximagesink (needs gstreamer 0.10.10)
Summary: Totem crashes if you resize the window when using ximagesink (needs gstreamer...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer
Version: rawhide
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Depends On: 208295
Blocks: FC6Update
TreeView+ depends on / blocked
 
Reported: 2006-09-09 01:00 UTC by David Nielsen
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 0.10.10-2.fc6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-22 17:47:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
backtrace of the crash (16.77 KB, text/plain)
2006-09-09 01:00 UTC, David Nielsen 		no flags Details
View All

Description David Nielsen 2006-09-09 01:00:51 UTC 
Description of problem:
To use totem and compiz at the same time you have to set the videosink to
ximagesink however doing that (even when using metacity) totem crashes if you
resize the window.

Version-Release number of selected component (if applicable):
gstreamer-0.10.9-2
gstreamer-plugins-good-0.10.4-1.fc6
totem-2.16.0-1.fc6

How reproducible:
100%

Steps to Reproduce:
1. set videosink to ximagesink
2. load video in totem
3. resize window
  
Actual results:
crash

Expected results:
succesfully resized image

Additional info:
Comment 1 David Nielsen 2006-09-09 01:00:51 UTC 
Created attachment 135892 [details]
backtrace of the crash
Comment 2 David Nielsen 2006-10-05 09:46:39 UTC 
This is fixed in gstreamer-0.10.10 - this bug can be closed once that package
gets updated (and hopefully pushed for FC6/FC5 stable)
Comment 3 Matthias Clasen 2006-10-05 17:42:14 UTC 
Thanks, that was my conjecture, but I didn't get around to testing it.
Comment 4 Alexander Larsson 2006-11-21 10:01:47 UTC 
Ok. Reassigning
Comment 5 Matthias Clasen 2006-11-22 17:47:36 UTC 
gstreamer-0.10.10 is in fc6-updates
Note You need to log in before you can comment on or make changes to this bug.