rhythmbox crashed with SIGSEGV in oil_init()

Bug #1225538 reported by Alexander Langanke
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

crashed on start

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7
Uname: Linux 3.10.0-0-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Sat Sep 14 01:53:09 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-06-26 (79 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130626)
MarkForUpload: True
ProcCmdline: rhythmbox
SegvAnalysis:
 Segfault happened at: 0x7fcea1f46071: mov 0x20(%rax),%rax
 PC (0x7fcea1f46071) 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 lpadmin plugdev sambashare sudo

Revision history for this message
Alexander Langanke (alexlanganke) 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.