Rhythmbox unresponsive when deleting music from ipod

Bug #331608 reported by Jonathan Lumb
4
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

When I try and delete multiple files from my iPod Nano (original version) in Rhythmbox, the screen fades to black and white for a number of seconds whilst it does the file operation. If I only delete 5 or 10 files then after a while Rhythmbox becomes responsive again and the screen comes back into colour. If I try and delete hundreds of songs then Rhythmbox becomes completely unresponsive and I have to force it to quit and start it up again.

Surely rhythmbox shouldn't become unresponsive just because I want to delete some files - it would make some sense to have a progress bar for deleting files in the same way as there is a progress bar for adding files to the iPod. Even if there is no progress bar, I would expect that you could continue to use Rhythmbox whilst the delete operation is in progess.

Some more info about my system below:

Description: Ubuntu 8.10
Release: 8.10

  已安装:0.11.6svn20081008-0ubuntu4.3
  候选的软件包:0.11.6svn20081008-0ubuntu4.3
  版本列表:
 *** 0.11.6svn20081008-0ubuntu4.3 0
        500 http://archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     0.11.6svn20081008-0ubuntu4 0
        500 http://archive.ubuntu.com intrepid/main Packages

Thanks for your help, please don't hesitate to ask for more info.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Jonathan Lumb (jonolumb) wrote :

Here is the backtrace as requested :-)

Revision history for this message
Sebastien Bacher (seb128) wrote :

does removing a file on the ipod using nautilus works correctly? are you sure it's stucked?

Revision history for this message
Jonathan Lumb (jonolumb) wrote :

removing files in nautilus is fine - basically the problem is that whilst it is deleting files from the iPod in Rhythmbox the program becomes incredibly slow or unresponsive - which I would consider to be undesirable and buggy behaviour. Likewise, when adding files to the iPod, Rhythmbox is incredibly slow and unresponsive.

Revision history for this message
Sebastien Bacher (seb128) wrote :

not confirming the issue there

Changed in rhythmbox:
status: Incomplete → New
Revision history for this message
Jonathan Lumb (jonolumb) wrote :

there is definitely an issue i'm afraid - otherwise the screen would not fade to black and white and the program become unresponsive - this is not behaviour that I would expect from any program and gives a bad impression to the end user - it might not be a major bug but something certainly needs changing.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try the same with Karmic ? Thanks in advance.

Changed in rhythmbox (Ubuntu):
status: New → Incomplete
Revision history for this message
Jonathan Lumb (jonolumb) wrote :

Hi Pedro

Unfortunately my iPod is broken so I am unable to do any further investigation into the mentioned issue for the time being - I'm not sure if anyone else has been affected by this bug?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the fast response Jonathan, it doesn't seems that anyone else is affected by this bug, I have an ipod and it works fine with rhythmbox, let's wait a bit in case someone else is facing a similar issue, thanks again.

Revision history for this message
Nigel Babu (nigelbabu) wrote :

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!

Revision history for this message
Cefn (6-launchpad-net-cefn-com) wrote :

I can confirm similar behaviour on my Ubuntu (Mint) installation, pushing a few hundred tunes using an iPod Touch and the ifuse packages, as described here...
http://fatbuttlarry.blogspot.com/2010/01/ipod-touch-iphone-3g-ubuntu-910-in-5.html

I appreciate that mine isn't a mainstream supported system, and these packages don't come from the package repository, but seems to be the only way to get a non-jailbroken iPod Touch to work with Linux at all, so I'd expect these to migrate to the core in a future Ubuntu release.

The greying out and unresponsiveness is the same. Eventually Rhythmbox becomes responsive again, but the transfer is running so slow that a 5 minute MP3 takes about 30 seconds to synchronise.

I don't know for sure where the slowness comes from, but I suspect it may be the same aspect, since Rhythmbox syncing to crippled Crapple iPod technology is the common factor. Happy to probe my system in whatever way you recommend. Let me know what tests I can run to reliably eliminate other speed issues (iFuse) from the investigation.

It's possible somehow the USB hub is being forced down to USB 1.0 or 1.1 speeds by something else on the same hub - I have a keyboard and mouse attached to it as well. Any ideas how to eliminate this possibility by monitoring runtime information in the system.

Revision history for this message
Omer Akram (om26er) wrote :

closing this bug now since the only other person that might have faced this issue forgot to subscribe to this bug report. :/

Changed in rhythmbox (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.