rhythmbox crashed with SIGABRT in do_sigtimedwait()

Bug #1283874 reported by Lacyc3
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Rhythmbox
Expired
Critical
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
Rhythmnox version: 3.0.1-1ubuntu10 0

While Rhythmnox played music, I clicked on Rhythmbox icon at indicator-sound to open it.

Expected: Open Rhythmbox window.
Happend: Crash

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.1-1ubuntu10
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 24 02:06:27 2014
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2014-01-29 (25 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128)
ProcCmdline: rhythmbox
Signal: 6
SourcePackage: rhythmbox
StacktraceTop:
 Py_FatalError () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
 _Py_CheckRecursiveCall () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
 PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
 PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0
Title: rhythmbox crashed with SIGABRT in Py_FatalError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Lacyc3 (lacyc3) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 do_sigtimedwait (timeout=<optimized out>, info=0x7feb0c00f868 <stderr>, set=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/../../../../../sysdeps/unix/sysv/linux/sigtimedwait.c:60
 __GI___sigtimedwait (set=<optimized out>, info=0x7feb0c00f868 <stderr>, timeout=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/../../../../../sysdeps/unix/sysv/linux/sigtimedwait.c:75
 ?? ()
 write () at ../sysdeps/unix/syscall-template.S:81
 PyThread_acquire_lock_timed (lock=0x7feb0bcc8cc3 <_IO_new_do_write+131>, microseconds=<optimized out>, intr_flag=2) at ../Python/thread_pthread.h:352

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
summary: - rhythmbox crashed with SIGABRT in Py_FatalError()
+ rhythmbox crashed with SIGABRT in do_sigtimedwait()
tags: removed: need-amd64-retrace
Revision history for this message
Lacyc3 (lacyc3) wrote :

Workaround: Disable MediaServer2 D-Bus plugin.

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thanks for reporting his issue. Upstream bug has been filed.

Changed in rhythmbox:
importance: Unknown → Critical
status: Unknown → Incomplete
Changed in rhythmbox:
status: Incomplete → Expired
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.

The upstream bug report was closed as the requested information was not provided to the Gnome developer(s).

Ubuntu 14.04 is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu please let us know otherwise this report can be left to expire in approximately 60 days time.

Paul White
[Ubuntu Bug Squad]

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

Bug report won't expire due to bug watch.
No reply to comment #8 from reporter so closing.

Changed in rhythmbox (Ubuntu):
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.