gstreamer-properties crashes with segfault with empty output pipeline

[Peter Fletcher]

Binary package hint: gnome-media

I have used gstreamer-properties to switch colours to fix a Video playback bug in Ubuntu, setting the video output pipeline to:

ffmpegcolorspace ! video/x-raw-yuv,format=(fourcc)YV12 ! xvimagesink

This worked OK, until the colours became swapped again.

I stupidly set the video output pipeline to an empty string, whereupon gstreamer-properties now crashes upon startup:

pfl@Jodie:~$ gstreamer-properties
gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink'
gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink'
Segmentation fault
pfl@Jodie:~$

Now I cannot try anything else.

Ubuntu: Hardy Heron

pfl@Jodie:~$ dpkg -S /usr/bin/gstreamer-properties
gnome-media: /usr/bin/gstreamer-properties
pfl@Jodie:~$ lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Peter Fletcher (peter-traal)]

Sebastien Bacher wrote:
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently. Thanks in advance for your cooperation and understanding.

So, you're basically saying: "Fuck off!"
Why do you have to take so long to say it?

-peter.

[Pedro Villavicencio (pedro)]

Peter, no, he's not saying that but it seems that you didn't understand the message, anyways, in order to maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind.

[Peter Fletcher (peter-traal)]

Pedro Villavicencio wrote:
> Peter, no, he's not saying that but it seems that you didn't understand
> the message, anyways, in order to maintain a respectful atmosphere,
> please follow the code of conduct -

I understood the message: what gives you the impression that I did not?

My apparent rudeness was a simple reaction to the fact that my bug report had been
closed, after I followed all the instructions requested before posting it, and without
any serious attempt to either read or reproduce the bug.

The request to submit further information about the bug should have occurred without
closing the bug, and it was clear that no attempt was made to reproduce or address
the bug.

The people who submit bugs in good faith are also volunteers, and deserve more than
a form letter reply followed by bug closure.

-peter.