rhythmbox crashed with SIGSEGV

Bug #508001 reported by Sokolov Sergey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

I was listening to music from iPod with Rhythmbox.
I closed Rhythmbox and apport warned a crash.

ProblemType: Crash
Architecture: amd64
Date: Fri Jan 15 18:30:20 2010
Disassembly: 0x7f2a9663edb2: Cannot access memory at address 0x7f2a9663edb2
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.6-1ubuntu6
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
Signal: 11
SourcePackage: rhythmbox
Stacktrace:
 #0 0x00007f2a9663edb2 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff07fc8120
StacktraceTop: ?? ()
Tags: lucid
Title: rhythmbox crashed with SIGSEGV
Uname: Linux 2.6.32-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x7f2a9663edb2: Cannot access memory at address 0x7f2a9663edb2
 PC (0x7f2a9663edb2) ok
 SP (0x7fff07fc8120) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
Sokolov Sergey (cleversokol-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f2a9663edb2 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff07fc8120
StacktraceSource: #0 0x00007f2a9663edb2 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in rhythmbox (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete
visibility: private → public
Revision history for this message
Sokolov Sergey (cleversokol-deactivatedaccount) wrote :
Kees Cook (kees)
description: updated
Revision history for this message
Omer Akram (om26er) wrote :

do you see a similar crash with latest ubuntu?

Changed in rhythmbox (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
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.