rhythmbox crashed with SIGSEGV in gethostbyname2_r()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
For some reason Rhythmbox doubled my library size and then started going through it again to remove all the fake duplicate entries. I restarted the program and the first time I did this it crashed immediately, causing this error.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sun Mar 18 20:33:46 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: rhythmbox
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f5b9e662bfe: lock xadd %eax,0x18(%rdi)
PC (0x7f5b9e662bfe) ok
source "%eax" ok
destination "0x18(%rdi)" (0x00000017) 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 /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
gethostbyname2_r () from /lib/x86_
Title: rhythmbox crashed with SIGSEGV in gethostbyname2_r()
UpgradeStatus: Upgraded to precise on 2012-01-28 (50 days ago)
UserGroups: adm admin audio cdrom dialout floppy lpadmin plugdev sambashare users video
| JG (jdogzz-g5) 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 #949771, 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.