rhythmbox crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: rhythmbox
I think I was browsing DAAP shares, then went back to my library. I tried to quit Rhythmbox, but it didn't close, and was otherwise responsive. After xkill'ing it, apport fired up this report.
Rhythmbox 0.12.7-0ubuntu7
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 23 10:16:14 2010
Disassembly: => 0xa0d29: Cannot access memory at address 0xa0d29
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
NonfreeKernelMo
Package: rhythmbox 0.12.7-0ubuntu7
ProcCmdline: rhythmbox
ProcEnviron:
LANG=en_NZ.utf8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xa0d29: Cannot access memory at address 0xa0d29
PC (0x000a0d29) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
?? ()
g_closure_invoke ()
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: rhythmbox crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
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. wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
Please try to obtain a backtrace manually following the instructions at http://