rhythmbox crashed with SIGSEGV in tdb_store()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Rhythmbox crashed while playing stream from the last.fm plugin. I tried to scroll and fast-forward and it first froze and then crashed.
I'm not sure if fast-forwarding within a streaming song is even supported, regardless of that, Rhythmbox shouldn't crash.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 12 14:17:21 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321)
ProcCmdline: rhythmbox
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fd18323d532: mov %ebx,(%rax)
PC (0x7fd18323d532) ok
source "%ebx" ok
destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
tdb_store () from /usr/lib/
?? () from /usr/lib/
Title: rhythmbox crashed with SIGSEGV in tdb_store()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Davor Capalija (davor-capalija) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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 #941434, 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.