Bug 114238

Summary:	iPod Module does not check free space on iPod Shuffle
Product:	[Applications] amarok	Reporter:	Rafael Kolless <rafael>
Component:	Collections/iPod iPhone	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED INTENTIONAL
Severity:	crash	CC:	matej
Priority:	NOR
Version:	1.3.3
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Rafael Kolless 2005-10-11 21:05:04 UTC

Version:           1.3.3 (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
OS:                Linux

When you upload tracks to the iPod (Shuffle) and you exceed the free space of the iPod it quits the transfer with a message that theres no space left. After this amarok hangs up with 100% CPU consuming and you must kill amarok by hand.

After this the iPod database is out of sync and you must rebuild the index with other apps like gtkpod to find orphaned files.

When you reattach the iPod later to amarok and you try to upload other tracks the naming convention is out of sync on the iPod and amarok. It tries to copy with kpodxxx.mp3 names already existing on the iPod. You must rename them and find a free number.

Comment 1 Rafael Kolless 2005-10-11 21:08:10 UTC

It would be usefull if amarok would check the remaining space on the iPod like gtkpod does and deny any upload that exceeds the free space on it.

Comment 2 Dan Meltzer 2005-10-23 04:37:10 UTC

This will probably come in 1.4 when we switch to libgpod for ipod support.

Comment 3 Mike Diehl 2005-11-03 04:31:55 UTC

Moving.

Comment 4 Martin Aumueller 2005-12-30 12:16:58 UTC

This problem is already fixed in amaroK 1.4-svn. However, as iPod support is completely reworked, this will not be backported to amaroK 1.3.

Comment 5 madman 2007-03-18 21:57:00 UTC

What about re-opening this bug for 1.4.5? I still have very similar problem on 1.4.5 (Kubuntu Feisty binaries). Upon reaching end of Shuffle's (1stGen) free space, amarok throws a bunch of popup messages about transfer error (IMHO it should cancel further transfers when out-of-disk-space occurs), then consumes 100% CPU for a few minutes and returns to normal state.

Could't this behaviour be fixed?