Ubuntu
rhythmbox package

rhythmbox crashed with SIGABRT in g_assertion_message()

Bug #1428626 reported by voron on 2015-03-05

This bug report is a duplicate of: Bug #1444580: rhythmbox crashed with SIGABRT in g_assertion_message() (hash_table->ref_count > 0). Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	rhythmbox (Ubuntu)	New	Medium	Unassigned

Bug Description

i configuring Rhythmbox addons and her crashed. system ubuntu-gnome15.04 alfa

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: rhythmbox 3.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar 5 14:50:36 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2015-03-04 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150303)
ProcCmdline: rhythmbox
Signal: 6
SourcePackage: rhythmbox
StacktraceTop:
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/rhythmbox/plugins/grilo/libgrilo.so
g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

voron (rshabashov) wrote on 2015-03-05:

#1

Dependencies.txt Edit (16.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (958 bytes, text/plain; charset="utf-8")
GstreamerVersions.txt Edit (6.4 KiB, text/plain; charset="utf-8")
LogAlsaMixer.txt Edit (356 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (290 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (142.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (833 bytes, text/plain; charset="utf-8")
Registers.txt Edit (732 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (10.4 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (31.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2015-03-05: Stacktrace.txt

#3

Stacktrace.txt Edit (13.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2015-03-05: StacktraceSource.txt

#4

StacktraceSource.txt Edit (8.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2015-03-05: StacktraceTop.txt

#5

StacktraceTop.txt Edit (1.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2015-03-05: ThreadStacktrace.txt

#6

ThreadStacktrace.txt Edit (23.2 KiB, text/plain)

Changed in rhythmbox (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2015-03-26:

#7

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

The issue seems to be due to the grilo plugin code

information type:

Private → Public

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1444580 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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