rhythmbox crashed with SIGABRT in Py_FatalError()

Bug #1578260 reported by Walter Garcia-Fontes
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Rhythmbox crashes systematically with the following steps:

1) Open Rhythmbox
2) Hear a podcast and put Rhythmbox into the background
3) When the podcast finishes, click on the app-indicator to put Rhythmbox in the foreground.

What should happen?: Rhythmbox should go to the foreground.
What happens actually? Rhythmbox crashes.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: rhythmbox 3.3-1ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 4 17:01:29 2016
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2015-10-17 (199 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: rhythmbox
Signal: 6
SourcePackage: rhythmbox
StacktraceTop:
 Py_FatalError () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 _Py_CheckRecursiveCall () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 _PyObject_CallMethodId () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
Title: rhythmbox crashed with SIGABRT in Py_FatalError()
UpgradeStatus: Upgraded to xenial on 2016-03-11 (54 days ago)
UserGroups: adm cdrom dip lpadmin mail plugdev sambashare sudo

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Py_FatalError () from /tmp/apport_sandbox_5qj46A/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 _Py_CheckRecursiveCall () from /tmp/apport_sandbox_5qj46A/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 PyObject_Call () from /tmp/apport_sandbox_5qj46A/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 _PyObject_CallMethodId () from /tmp/apport_sandbox_5qj46A/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
 flush_std_files () from /tmp/apport_sandbox_5qj46A/usr/lib/x86_64-linux-gnu/libpython3.5m.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 : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

I didn't have debugging symbols, I have downloaded them and will try to reproduce and generate a useful stacktrace.

Changed in rhythmbox (Ubuntu):
status: New → Invalid
summary: - rhythmbox crashed with SIGABRT in Py_FatalError()
+ rhythmbox crashed
summary: - rhythmbox crashed
+ rhythmbox crashed with SIGABRT in Py_FatalError()
Changed in rhythmbox (Ubuntu):
status: Invalid → New
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

I attach anotgher stacktrace produced with debug symbols installed

Changed in rhythmbox:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in rhythmbox:
status: Confirmed → Incomplete
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

This is a bug in rhythmbox-plugin-radio-browser. If this pluing is disabled I cannot reproduce it. I have reported the bug in the issue tracker for this plugin:
https://github.com/fossfreedom/radio-browser/issues/18

no longer affects: rhythmbox
Revision history for this message
rithik g (gkrithi) wrote :

crash is in external plugin.

nothing to do with rhythmbox code. resolving as invalid.

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