Rhythmbox freezes after a period of time

Bug #43656 reported by Andrew Conkling on 2006-05-08
10
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

Rhythmbox has been unusable for me for a while now on my laptop (a Dell Inspiron 6000). When I start it, it will freeze (where the window stays but the GUI is not refreshed), sometimes immediately, sometimes after as much as 10 minutes.

When this happens, I have to force quit the window (via metacity) and I can't kill the process, even using -9. The only way to kill the process (and try to run RB again) is to reboot.

FWIW, I have similar aberrant behavior with CDs/DVDs in my drive: sporadically, when I insert them, they will not load on the desktop, and I'll have to reboot to try again. (I'm not sure if that's exactly related, or a separate issue.)

I have been unable to get a backtrace on RB; my gdb output follows:

Starting program: /usr/bin/rhythmbox
[Thread debugging using libthread_db enabled]
[New Thread -1227364672 (LWP 6223)]
[New Thread -1249305680 (LWP 6232)]
[New Thread -1249776720 (LWP 6248)]
[Thread -1249776720 (LWP 6248) exited]
[New Thread -1249776720 (LWP 6249)]
[Thread -1249776720 (LWP 6249) exited]
[New Thread -1249776720 (LWP 6252)]
[New Thread -1258751056 (LWP 6253)]
[Thread -1258751056 (LWP 6253) exited]
[New Thread -1258751056 (LWP 6254)]
[Thread -1249776720 (LWP 6252) exited]
[Thread -1258751056 (LWP 6254) exited]
[New Thread -1258751056 (LWP 6256)]
[New Thread -1249776720 (LWP 6257)]
[New Thread -1268778064 (LWP 6258)]
[Thread -1258751056 (LWP 6256) exited]
[Thread -1268778064 (LWP 6258) exited]
[New Thread -1268778064 (LWP 6263)]
[New Thread -1258751056 (LWP 6264)]
[New Thread -1277170768 (LWP 6265)]
[New Thread -1285563472 (LWP 6266)]
[New Thread -1293956176 (LWP 6267)]
[New Thread -1302348880 (LWP 6268)]
[New Thread -1310741584 (LWP 6269)]
[New Thread -1319134288 (LWP 6270)]
[New Thread -1327526992 (LWP 6271)]
[New Thread -1335919696 (LWP 6272)]
[New Thread -1344312400 (LWP 6273)]
[Thread -1268778064 (LWP 6263) exited]
[New Thread -1268778064 (LWP 6274)]
[Thread -1268778064 (LWP 6274) exited]
[Thread -1258751056 (LWP 6264) exited]
[Thread -1277170768 (LWP 6265) exited]
[Thread -1285563472 (LWP 6266) exited]
[Thread -1293956176 (LWP 6267) exited]
[Thread -1302348880 (LWP 6268) exited]
[Thread -1310741584 (LWP 6269) exited]
[Thread -1319134288 (LWP 6270) exited]
[Thread -1327526992 (LWP 6271) exited]
[Thread -1335919696 (LWP 6272) exited]
[Thread -1344312400 (LWP 6273) exited]
thread_db_get_info: cannot get thread info: generic error
(gdb) thread apply all bt full
[New Thread -1344312400 (LWP 6290)]
Can't attach LWP 6290: Operation not permitted

I have the same configuration on my desktop, where I am not noticing this problem.

Andrew Conkling (andrewski) wrote :

By the way, I have tried moving my ~/.gnome2/rhythmbox folder to start with a default configuration and the same problem occurs.

Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu do you use? Could you run "rhythmbox -d" to note what happens exactly? Could you get a backtrace with rhythmbox-dbg installed?

Changed in rhythmbox:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Andrew Conkling (andrewski) wrote :

This is in Dapper, and my gdb was -dbg. However, I just found out through a long and arduous process that my CD/DVD drive in this laptop is bad. I just now took out the drive and restarted and haven't noticed the problem with RB. (Last time I tried was yesterday.)

I'm closing this out and will reopen it if necessary. Thanks for following up Seb; you rock.

Changed in rhythmbox:
status: Needs Info → Rejected
Sebastien Bacher (seb128) wrote :

Thank you for replying and closing the bug. It's possible that rhythmbox was trying to determine if you had an audio CD ready to play and hanging on the drive reply

Andrew Conkling (andrewski) wrote :

On 5/28/06, Sebastien Bacher <email address hidden> wrote:
> Thank you for replying and closing the bug. It's possible that rhythmbox
> was trying to determine if you had an audio CD ready to play and hanging
> on the drive reply

Would that be something that should be filed upstream? Or is handling bad hardware outside the scope of the software? ;)

Sebastien Bacher (seb128) wrote :

you can maybe try to bug upstream, but they already have lot of real programs bugs to fix and new feature to code, I'm not sure on how much they want to spend to workaround broken material, and how much they can do anyway if a system call doesn't return as expected

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers