GNOME Bugzilla – Bug 321240
[PLUGIN-MOVE] dfbvideosink should be moved to -good
Last modified: 2013-08-22 13:03:58 UTC
it has documentation, examples, it has all things a video sink could implement and it's so neat !
yes!
Do it! Do it!
Maybe fix this first: wim@wtay:~/gst/head/gstreamer$ gst-launch videotestsrc ! dfbvideosink Setting pipeline to PAUSED ... ---------------------- DirectFB v0.9.24 --------------------- (c) 2000-2002 convergence integrated media GmbH (c) 2002-2004 convergence GmbH ----------------------------------------------------------- (*) DirectFB/Core: Single Application Core. (2006-06-14 07:02) (*) Direct/Memcpy: Using MMXEXT optimized memcpy() (!) DirectFB/core/vt: Error opening `/dev/tty0'! --> Permission denied (!) DirectFB/Core: Could not initialize 'system' core! --> Initialization error! Pipeline is PREROLLING ... (!) [ 8212: 0.000] --> Caught signal 11 (at 0x14, invalid address) <-- Killed wim@wtay:~/gst/head/gstreamer$
Somehow it starts streaming and then fails in buffer_alloc. Program received signal SIGSEGV, Segmentation fault.
+ Trace 69833
Thread NaN (LWP 9176)
Created attachment 69984 [details] Debug log output of gst-launch-0.10 --gst-debug=dfbvideosink:5 videotestsrc ! dfbvideosink >/tmp/trace.log 2>&1
the two commits make me happy again: * ext/directfb/dfbvideosink.c: (gst_dfbvideosink_change_state), (gst_dfbvideosink_buffer_alloc): Don't try allocating if we are not setup yet. Fail changing state if setup fails. * ext/directfb/dfbvideosink.c: (gst_dfbvideosink_change_state), (gst_dfbvideosink_buffer_alloc): Post an error message.
Ok, so what's missing now to get this moved other than someone doing the move? :)
Well, it looks OK from my side... marking as a blocker for the coming releases.
bug #503743 should be done before I guess... as it might need API changes. Unmarking this bug as blocker until this is done and we have a second review.
The cause of bug #517854 should also be investigated and fixed before a move.
Is this plugin ready to be moved now?
Hey Christian :) I haven't checked it in a long long time. I assume it's not as good as it used to be compared to today's GStreamer standards. It would need some QA/polish before that happens IMHO. Cheers,
Anybody planning to work on this? Does it make sense to keep this bug open for now?
Needs porting first (see bug #321240). I would suggest we close this bug until someone expresses some interest again and willingness to work on it to achieve the move.