rhythmbox crashed with SIGSEGV

[UGN]

Binary package hint: rhythmbox

i press quit on systray icon, but see rhytmbox in processes 139mb memory and close process

ProblemType: Crash
Architecture: i386
Date: Sat Jan 16 11:18:47 2010
Disassembly: 0x470de9: Cannot access memory at address 0x470de9
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100107)
Package: rhythmbox 0.12.6-1ubuntu6
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=(custom, user)
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
Signal: 11
SourcePackage: rhythmbox
Stacktrace:
 #0 0x00470de9 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf910b0c
StacktraceTop: ?? ()
Tags: lucid
Title: rhythmbox crashed with SIGSEGV
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x470de9: Cannot access memory at address 0x470de9
 PC (0x00470de9) ok
 SP (0xbf910aa0) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

[Apport retracing service (apport)]

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

[Pedro Villavicencio (pedro)]

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.

[Nigel Babu (nigelbabu)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!