totem-gstreamer crashed with SIGSEGV

Bug #190478 reported by Kai Schroeder
6
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: totem

totem crashed when I moved the volume control.

ProblemType: Crash
Architecture: amd64
Date: Sat Feb 9 16:47:21 2008
Disassembly: 0x0:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/totem-gstreamer
NonfreeKernelModules: nvidia
Package: totem-gstreamer 2.21.92-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: totem
ProcCwd: /home/kai
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/cuda/bin:/home/kai/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/gstreamer-0.10/libgstvolume.so
 ?? () from /usr/lib/libgstbase-0.10.so.0
 ?? () from /usr/lib/libgstbase-0.10.so.0
 ?? () from /usr/lib/libgstreamer-0.10.so.0
Title: totem-gstreamer crashed with SIGSEGV
Uname: Linux main 2.6.24-7-generic #1 SMP Thu Feb 7 00:56:31 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv netdev plugdev powerdev pulse-rt scanner video

Revision history for this message
Kai Schroeder (kai-schroeder) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
volume_transform_ip (base=0xc167b0, outbuf=0xc336b0) at gstvolume.c:709
gst_base_transform_handle_buffer (trans=0xc167b0, inbuf=0xc336b0,
gst_base_transform_chain (pad=0xc502e0, buffer=0xc336b0)
gst_pad_chain_unchecked (pad=0xc502e0, buffer=0xc336b0) at gstpad.c:3518

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Kai Schroeder (kai-schroeder) wrote :

looks like this is not reproducible, so I can't provide any better backtrace at the moment.

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

Ok, thanks, i'll set as incomplete for now until you can provide us a better trace, thanks.

Changed in totem:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
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 totem:
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.