totem crashed with SIGSEGV (Youtube search term incl. single quote)

Bug #821878 reported by Moritz Naumann
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gstreamer0.10 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I was searching for a song/track on Youtube (from within Totem). The search term included a single quote. As soon as I submitted the search Totem crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libgstreamer0.10-0 0.10.32-3ubuntu3.1
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
Date: Sat Aug 6 11:38:00 2011
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: totem
ProcEnviron:
 LANGUAGE=de_DE:en
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe63ce6047e: mov (%r12),%rsi
 PC (0x7fe63ce6047e) ok
 source "(%r12)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gstreamer0.10
StacktraceTop:
 ?? () from /usr/lib/libgdata.so.11
 ?? () from /usr/lib/libgdata.so.11
 ?? () from /usr/lib/libgdata.so.11
 ?? () from /usr/lib/libgdata.so.11
 ?? () from /usr/lib/libgdata.so.11
Title: totem crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-06-20 (46 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Moritz Naumann (mnaumann) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gstreamer0.10 (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

package gstreamer0.10-gconf does not exist, ignoring

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Moritz Naumann (mnaumann) wrote :

I think the retracing service is wrong here.

$ sudo zgrep -F gstreamer0.10-gconf /var/log/apt/{history,term}.log*
$

I don't think I ever had a package "gstreamer0.10-gconf" installed. I do, however, keep my system updated on a daily basis.

sudo apt-get update && sudo apt-get dist-upgrade
indicates that all packages are current. My 'apt-cache policy' output is attached.

The latest change to any sources.list include file was on July 20th, this bug was filed on Aug 08th.

$ sudo ls -lt /etc/apt/sources.list* | head -n1
-rw-r--r-- 1 root root 1154 Jul 20 00:57 /etc/apt/sources.list
$

I assume this bug can be set to be public now.

visibility: private → public
Revision history for this message
Moritz Naumann (mnaumann) wrote :

I should have tried to reproduce the bug first. It turns out I cannot, so please feel free to close it.

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.