rhythmbox crashed with SIGSEGV in start_thread() on changing podcast directory

Bug #1031233 reported by Heiko Roth
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

before changed music directory to ~/Music
crahsed on chanhing podcast directory afterwards to ~/Documents

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Tue Jul 31 09:44:55 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: rhythmbox
SegvAnalysis:
 Segfault happened at: 0x7f9b1338a0d0: mov (%rax),%rsi
 PC (0x7f9b1338a0d0) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
Title: rhythmbox crashed with SIGSEGV in start_thread()
UpgradeStatus: Upgraded to quantal on 2012-07-21 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Heiko Roth (roth-egotec) 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 #1029333, 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.

visibility: 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.