claims ipod needs initialization
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rhythmbox |
Expired
|
Medium
|
|||
rhythmbox (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: rhythmbox
Every time I connect my iPod I'm greeted with a prompt stating:
"Do you want to initialize your iPod?
Rhythmbox has detected a device that is probably an uninitialised or corrupted iPod. It must be initialised before Rhythmbox can use it, but this will destroy any song metadata already present. If you wish Rhythmbox to initialise the iPod, please fill in the information below. If the device is not an iPod, or you do not wish to initialise it, please click cancel."
The ironic bit is that while this prompt is present Rhythmbox proceeds to play audio from the iPod without issue.
I have added an ext3 partition to the iPod, but this partition has been present during the iPod's use with previous releases and never caused a problem such as this.
$ sudo fdisk -l /dev/sdb
Note: sector size is 2048 (not 512)
Disk /dev/sdb: 8120 MB, 8120172544 bytes
250 heads, 62 sectors/track, 255 cylinders
Units = cylinders of 15500 * 2048 = 31744000 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 3 92876 0 Empty
/dev/sdb2 4 215 6572000 b W95 FAT32
/dev/sdb3 216 255 1240000 83 Linux
$ mount | grep sdb
/dev/sdb2 on /media/iPod type vfat (rw,nosuid,
/dev/sdb3 on /media/key-backup type ext3 (rw,nosuid,
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelMo
Package: rhythmbox 0.12.0-0ubuntu4
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: rhythmbox
Uname: Linux 2.6.28-11-generic x86_64
Changed in rhythmbox: | |
status: | Unknown → New |
Changed in rhythmbox: | |
importance: | Unknown → Medium |
Changed in rhythmbox: | |
status: | New → Expired |
thank you for your bug report, the issue is an upstream one and should be sent to bugzilla.gnome.org by somebody having access to a device triggering the issue