totem crashed with SIGSEGV in g_rec_mutex_get_impl()

Bug #917318 reported by THAC0
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Description: Ubuntu precise (development branch)
Release: 12.04

I closed totem, it appeared to close fine, but then I got a crash report dialogue.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: totem 3.0.1-0ubuntu15
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
Date: Mon Jan 16 19:15:52 2012
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120112)
ProcCmdline: totem
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7d6fe65d14 <g_rec_mutex_lock+4>: mov (%rdi),%rax
 PC (0x7f7d6fe65d14) ok
 source "(%rdi)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 g_rec_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_static_rec_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstplaybin.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstplaybin.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstplaybin.so
Title: totem crashed with SIGSEGV in g_rec_mutex_lock()
UpgradeStatus: Upgraded to precise on 2012-01-13 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
THAC0 (gunjam) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_rec_mutex_get_impl (rec_mutex=0xaaaaaaaaaaaaaaaa) at /build/buildd/glib2.0-2.31.8/./glib/gthread-posix.c:288
 g_rec_mutex_lock (mutex=0xaaaaaaaaaaaaaaaa) at /build/buildd/glib2.0-2.31.8/./glib/gthread-posix.c:377
 g_static_rec_mutex_lock (mutex=0x7f7d73ac0210) at /build/buildd/glib2.0-2.31.8/./glib/deprecated/gthread-deprecated.c:712
 gst_play_sink_get_sink (playsink=0x7f7d73ac00c0, type=GST_PLAY_SINK_TYPE_VIDEO) at gstplaysink.c:681
 gst_play_bin_get_current_sink (playbin=0x7f7d73ab8a00, elem=0x7f7d73ab9110, dbg=0x7f7d58c02faa "video", type=<optimized out>) at gstplaybin2.c:1972

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 totem (Ubuntu):
importance: Undecided → Medium
summary: - totem crashed with SIGSEGV in g_rec_mutex_lock()
+ totem crashed with SIGSEGV in g_rec_mutex_get_impl()
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in totem (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in totem (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for totem (Ubuntu) because there has been no activity for 60 days.]

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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