cheese crashed with SIGSEGV in gst_pad_push()

Bug #187486 reported by Ryan Rushton
12
Affects Status Importance Assigned to Milestone
gstreamer0.10 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: cheese

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

2.21.5-0ubuntu1

Start Cheese, it shows the initial cheese window and then pauses, on occasion the video will show. Takes about 15-30 seconds then segfaults.

ProblemType: Crash
Architecture: i386
Date: Wed Jan 30 18:03:48 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/cheese
NonfreeKernelModules: cdrom
Package: cheese 2.21.5-0ubuntu1
PackageArchitecture: i386
ProcCmdline: cheese
ProcCwd: /home/ryan
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
Signal: 11
SourcePackage: cheese
StacktraceTop:
 ?? () from /usr/lib/gstreamer-0.10/libgstvideo4linux2.so
 ?? ()
 ?? ()
 ?? ()
 gst_pad_push () from /usr/lib/libgstreamer-0.10.so.0
Title: cheese crashed with SIGSEGV in gst_pad_push()
Uname: Linux thelaptop 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner video
SegvAnalysis:
 Segfault happened at: 0xb59d3b67 <g_param_spec_flags@plt+48667>: mov %eax,0x14(%edi)
 PC (0xb59d3b67) ok
 source "%eax" ok
 destination "0x14(%edi)" (0x00000014) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

Revision history for this message
Ryan Rushton (ryancr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gst_v4l2src_create (src=0x832c210, buf=0xb3bf12f4) at gstv4l2src.c:1054
?? () from /usr/lib/libgstbase-0.10.so.0
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in cheese:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Ryan Rushton (ryancr) wrote :

Backtrace

Revision history for this message
Ryan Rushton (ryancr) wrote :

Valgrind

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

reassigning to the libgstreamer0.10-0 package, marking as new...

Changed in cheese:
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? May you please try the same with Karmic? Thanks in advance.

Changed in gstreamer0.10 (Ubuntu):
status: New → Incomplete
Kees Cook (kees)
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gstreamer0.10 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.