rhythmbox crashed with SIGSEGV

Bug #1052184 reported by Mike L
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running the latest Quantal development branch 64 bit with all the updates. Let me know if you guys need any more info.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu4
Uname: Linux 3.5.4-030504-generic x86_64
ApportVersion: 2.5.2-0ubuntu1
Architecture: amd64
Date: Mon Sep 17 16:54:18 2012
Disassembly: => 0x7f5d62605d4c: Cannot access memory at address 0x7f5d62605d4c
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
LogAlsaMixer:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
ProcCmdline: rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f5d62605d4c: Cannot access memory at address 0x7f5d62605d4c
 PC (0x7f5d62605d4c) ok
 Stack memory exhausted (SP below stack segment)
 SP (0x7f5cbb9bf5e0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Mike L (mikerl) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libcdparanoia0: package version 3.10.2+debian-11 dbgsym version 3.10.2+debian-10ubuntu1
outdated debug symbol package for libjack-jackd2-0: package version 1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1 dbgsym version 1.9.8~dfsg.1-1ubuntu1
firefox version 16.0~b3+build1-0ubuntu0.12.10.1~mfn1 required, but 15.0.1+build1-0ubuntu2 is available
python-gi version 3.3.91-1 required, but 3.3.92-1 is available
outdated debug symbol package for libcap-ng0: package version 0.6.6-2ubuntu1 dbgsym version 0.6.6-1ubuntu1
python-gobject version 3.3.91-1 required, but 3.3.92-1 is available
firefox-globalmenu version 16.0~b3+build1-0ubuntu0.12.10.1~mfn1 required, but 15.0.1+build1-0ubuntu2 is available
outdated debug symbol package for libfile-fcntllock-perl: package version 0.14-2 dbgsym version 0.14-1build1
python3-gi version 3.3.91-1 required, but 3.3.92-1 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.