Bug 682726 – crash viewing ogg properties

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 682726 - crash viewing ogg properties


Summary:	crash viewing ogg properties


Status:	RESOLVED INCOMPLETE

Product:	GStreamer
Classification:	Platform
Component:	gst-plugins-base
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	NONE
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-08-26 15:05 UTC by William Jon McCann
Modified:	2012-10-18 10:14 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
backtrace of crash (1.88 KB, text/plain) 2012-08-26 15:05 UTC, William Jon McCann	Details
bt of first critical warning (1.81 KB, text/plain) 2012-08-26 15:05 UTC, William Jon McCann	Details

Description William Jon McCann 2012-08-26 15:05:09 UTC

Created attachment 222470 [details]
backtrace of crash

When I try to open the properties dialog for an ogg file it crashes.

Comment 1 William Jon McCann 2012-08-26 15:05:40 UTC

Created attachment 222471 [details]
bt of first critical warning

Comment 2 Cosimo Cecchi 2012-08-27 12:36:39 UTC

-> totem

The Audio properties page is provided by Totem (and the backtrace seems to be crashing inside GStreamer)...make sure you have the latest gstreamer, and all the gstreamer plugins, from git master first though.

Comment 3 Tim-Philipp Müller 2012-09-25 23:50:46 UTC

Does this still happen? Are you using 1.0.0 or git master for all GStreamer modules?

Does

  gst-launch-1.0 playbin uri=file:///path/to/file.ogg

also crash?

Comment 4 Tim-Philipp Müller 2012-10-18 10:14:01 UTC

Assume this was caused by modules being out of sync with each other and still changing API/ABI in the 0.11.x days.

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!