Bug 133468

Version:           1.4.2 (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages

I have an iPod Nano 1GB, formatted to HFS+, with /dev/sda3 mounted at /mnt/ipod via fstab. If the partition is completely empty (e.g. if I do rm -rf /mnt/ipod/* while it is mounted), I can start amaroK (on my PPC Powerbook G4 running Kubuntu 6.06 LTS) and mount the iPod, which I have added as a manual media device with the iPod type. amaroK then asks me to initialize the iPod, after which I can transfer music to it.

However, as soon as I restart the iPod, it reboots and prompts me for the initial configuration (in my case, only the language setting). The iPod works fine, however, amaroK crashes as soon as I attempt to connect the iPod again (which is at startup, if it is mounted already, or after pressing the connect button when mounting the iPod while amaroK is running).

This only occurs if amaroK is restarted once (connecting a "configured" iPod works if it is done in the same amaroK session it was initialized in).

I have copied all contents of the iPod to a temporary directory before and after the iPod configuration, this is the output of 

$ diff -r ipodtainted/ ipodfresh/
Only in ipodtainted/: Calendars
Only in ipodtainted/: Contacts
Only in ipodtainted/iPod_Control: Accessories
Only in ipodtainted/iPod_Control: Device
Only in ipodtainted/: Notes

The following files are in those directories:

$ find ipodtainted/Calendars/ ipodtainted/Contacts/ ipodtainted/iPod_Control/Accessories/ ipodtainted/iPod_Control/Device/ ipodtainted/Notes/ -type f
ipodtainted/Contacts/ipod_created_instructions.vcf
ipodtainted/Contacts/ipod_created_sample.vcf
ipodtainted/iPod_Control/Device/clock
ipodtainted/iPod_Control/Device/Preferences
ipodtainted/iPod_Control/Device/radio
ipodtainted/iPod_Control/Device/SysInfo
ipodtainted/Notes/Instructions

** WORKAROUND **
Here is the workaround I found: erasing the file iPod_Control/Device/SysInfo will prevent amaroK from crashing, also the iPod will not reboot and reconfigure when ejected. If it is, however, rebooted manually, a new SysInfo file will be created (deleting it causes amaroK to work again). I'm guessing that this is a libgpod problem, since gtkpod will segfault if SysInfo is present (and work if not).

I could not find a bugtracker for libgpod, maybe someone from the amaroK team has better access to these kind of things? I'm not sure if this error occurs on the x86 version, too. Since the crash is fairly noticeable, I'm guessing it is ppc-only, which recieves a lot less testing.

The amarok version used was 1.4.2, with packages built from edgy source packages (binary package version is 1.4.2-0ubuntu3) - the ubuntu2 packages won't start on ppc, a bug that has been fixed in ubuntu2.