rhythmbox crashed with SIGSEGV in oil_init()

Bug #1229702 reported by John Przybytek
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

rhythmbox:
  Installed: 2.99.1-0ubuntu1
  Candidate: 2.99.1-0ubuntu1
  Version table:
 *** 2.99.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

I expected the package to play music

Instead it just closed

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 24 08:44:14 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-09-17 (6 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
MarkForUpload: True
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fcb04a38071: mov 0x20(%rax),%rax
 PC (0x7fcb04a38071) ok
 source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/liboil-0.3.so.0
 oil_init () from /usr/lib/x86_64-linux-gnu/liboil-0.3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
Title: rhythmbox crashed with SIGSEGV in oil_init()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

Revision history for this message
John Przybytek (jprzybytek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1226807, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.