Rhythmbox crashes upon launch

Also, the System Monitor indicates that- even after closing the debug console- rhythmbox is still running.

Process name | Status | Virtual Memory
Rhythmbox | Uninterruptible | 63.2 MiB

The process cannot be terminated, even with 'sudo killall rhythmbox'.

After restarting the machine, Rhythmbox appears to work fine. The unpredictability of the crash is a problem itself.

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

i followed the instructions for a backtrace. since rhythmbox starts up, then crash, but the process is still running as "uninterruptible", i followed the instructions on how to attach GDB to an already running program. however, when i entered the command 'attach 6709', gdb stoped working. i waited for about 10 minutes, but this action never finished.

so, i guess i will have to launch rhythmbox from gdb and just hope that it crashes?

i launched rhythmbox from gdb. it froze, and i clicked the Exit button. a dialogue appeared asking whether or not i wanted to force quit. i force-quit the application. however, the process did not end, so i was unable to continue the backtrace. this screen shot

http://i103.photobucket.com/albums/m128/envyouraudience/rb_backtrace.png

show that 1) rhythmbox was not open, 2) the tray icon was gone, 3) the process "rhythmbox" was running and uninterruptible, 4) the gdb prompt assumed that the program did not crash. therefore, i believe that it is impossible to get a backtrace for this problem. nevertheless, i attached the output.

did you type "continue" as documented on https://wiki.ubuntu.com/Backtrace after attaching gdb?

i couldn't do that because gdb could not be attached. i assumed that when it ahd been attached, the a new line would show up with (gdb), then i would be able to enter a command. this screenshot shows what the terminal looked like 10 minutes after i tried to attacg gdb:

http://i103.photobucket.com/albums/m128/envyouraudience/gbd_attach.png

as you can see, the (gdp) prompt did not show up again after i tried to attach the process. therefore, i must assume that gdb could not attah itself to the process.

thinking that i had done something wrong, i tried to attach gdp again, and this time i typed "continue" EVEN THOUGH the gdb prompt did NOT show up after i entered the attach command. this screenshot shows what happened:

http://i103.photobucket.com/albums/m128/envyouraudience/gpd_nottch.png

nevertheless, i attached the output.

You might want to run the software directly under the debugger, "gdb rhythmbox" and then type "run"

isn't that the same thing as i mention in this comment

https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/121424/comments/5

the comment you indicate has no crash information, without a stacktrace nor a wait to trigger the bug it's not easy to work on it

you need to read my comments more carefully.

1. i tried both methods (A. -attaching gdb to rhythmbox, and B.- running rhythmbox from gdb)

2. in A: i launched rhythmbox from gdb. rhythmbox crashed, but the process was uninterruptible.
http://i103.photobucket.com/albums/m128/envyouraudience/rb_backtrace.png

3. in B: gdb did not attach to the process as it was uninterruptible.
http://i103.photobucket.com/albums/m128/envyouraudience/gpd_nottch.png

They still have no crash information and there is no easy way to trigger the bug

yes- i understand that. so what am i supposed to do now?

you can open a bug on bugzilla.gnome.org if you want, maybe upstream will have a better idea since they write the code, otherwise trying to figure a way to trigger the bug would be useful to work on it

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.