totem-gstreamer crashed with SIGSEGV in g_object_set_valist()

Bug #179752 reported by don hardaway
10
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: totem

The movie player froze after watching a small MOV file.

ProblemType: Crash
Architecture: amd64
Date: Tue Jan 1 17:05:56 2008
Disassembly: 0x0:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/totem-gstreamer
NonfreeKernelModules: nvidia
Package: totem-gstreamer 2.21.5-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: totem file:///home/hardaway/Desktop/100_3677.MOV
ProcCwd: /home/hardaway
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? ()
 g_object_set_valist ()
 g_object_set () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
Title: totem-gstreamer crashed with SIGSEGV in g_object_set_valist()
Uname: Linux hardaway-laptop 2.6.24-2-generic #1 SMP Thu Dec 20 17:58:55 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
don hardaway (don-hardaway) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
g_object_set_valist () from /usr/lib/libgobject-2.0.so.0
g_object_set () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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 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.