rhythmbox crashed with SIGSEGV in oil_init()

Bug #1235630 reported by José Ignacio
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

h

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sat Oct 5 13:08:01 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-04-01 (187 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130328)
MarkForUpload: True
ProcCmdline: rhythmbox
ProcEnviron:
 LANGUAGE=es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x83516e28: mov 0x10(%eax),%edx
 PC (0x83516e28) ok
 source "0x10(%eax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0
 oil_init () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/i386-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
José Ignacio (jignacio-igualada) 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-i386-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.