rhythmbox crashed with SIGSEGV in sem_post@@GLIBC_2.1()

Bug #1199159 reported by jesus
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

rhythmbox falló cuando pare la reproducción de una canción de un CD de audio e intenté reproducir otra del mismo CD.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
Date: Mon Jul 8 23:22:49 2013
ExecutablePath: /usr/bin/rhythmbox
MarkForUpload: True
ProcCmdline: rhythmbox /run/user/1000/gvfs/cdda:host=sr0/Track\ 1.wav
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7374e15 <sem_post@@GLIBC_2.1+5>: mov (%ebx),%eax
 PC (0xb7374e15) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 sem_post@@GLIBC_2.1 () from /lib/i386-linux-gnu/libpthread.so.0
 PyThread_release_lock () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0
 PyEval_ReleaseLock () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0
 PyThreadState_DeleteCurrent () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0
 PyGILState_Release () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0
Title: rhythmbox crashed with SIGSEGV in sem_post@@GLIBC_2.1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
jesus (jesgartiel) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 sem_post@@GLIBC_2.1 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/sem_post.S:41
 PyThread_release_lock () from /tmp/apport_sandbox_ojfKPQ/usr/lib/i386-linux-gnu/libpython2.7.so.1.0
 PyEval_ReleaseLock () from /tmp/apport_sandbox_ojfKPQ/usr/lib/i386-linux-gnu/libpython2.7.so.1.0
 PyThreadState_DeleteCurrent () from /tmp/apport_sandbox_ojfKPQ/usr/lib/i386-linux-gnu/libpython2.7.so.1.0
 PyGILState_Release () from /tmp/apport_sandbox_ojfKPQ/usr/lib/i386-linux-gnu/libpython2.7.so.1.0

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 rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
jesus (jesgartiel) wrote :

cuando reproduzco una canción desde la disquetera con Rhythmbox , termina la canción y comienza la lista de reproducción por su cuenta, sin recibir la orden, cuando intento pararlo tarda en ejecutar la orden más de 20 segundos. Rhythmbox carga todos los discos a la lista de reproducción sin mi permiso. El reproductor es bueno , salvo en estos detalles. Gracias otra vez. Cada día estoy más satisfecho de Ubuntu, un saludo a las personas que lo hacen posible.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Artyom Kazak (artyom-kazak) wrote :

For me, Rhythmbox crashes just when I try to open it. However, if I delete its music library (rhythmdb.xml file), it loads normally, rebuilds the library… and crashes again after I restart it.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue seems to be due to python code, likely due to some plugin loaded

Revision history for this message
Hosdo (lorepanta) wrote :

Checked also bug #1193525, seems like it's not just "Zeitgeist" related. I'm running with almost any Plugin disabled, only MTP and Ipod support are on.

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.