[Bug 362182] [NEW] Amarok 2 lost support for iPhone-like devices - Choice between 2 and 1.4?
Nico
nico at youplala.net
Thu Apr 16 08:01:34 UTC 2009
Public bug reported:
Binary package hint: amarok
Hello,
I have started the move from Intrepid to Jaunty on a couple of machine.
And I have discovered the available Amarok is now 2.0.2, the 1.4 branch
is not there anymore.
This is annoying me because I have lost the ability to sync my iPod
Touch (like an iPhone) with an advanced music manager.
Amarok 2 tries to be as automatic and as cross-platform as possible.
It relies on Solid for media player detection.
Under Linux Solid relies on HAL to detect media players
HAL only sees real hardware, like disks or USB mass storage devices.
IPhones or iPod Touches are used through FUSE mounts, using SSH (WiFi) or iFuse (USB cables).
FUSE mounts are not hardware mounts, really, so they are not reported back to HAL.
So Solid does not see the iPhone.
So Amarok does not see the iPhone.
I am trying to stir some ideas with the Amarok devs on the Amarok
Mailing list. It looks like that whatever outcome rises out of this will
not be in time for this Ubuntu release cycle (and I am worried that my
bug is anyway coming way too late into the party anyway...).
GTKPOD relies on Gnome VFS to see mounts. Gnome VFS sees FUSE mounts. So Gnome VFS sees the iPhone. So GTKPOD sees the iPhone.
GTKPOD manages the iPhone properly using the database and libgpod.
But GTKPOD, however, is not really comparable to Amarok in terms of
music management.
Rhythmbox does not see the iPhone.
Banshee does not see the iPhone.
So in Jaunty, GTKPOD is the sole working, if not excellent, solution for
iPhone-like device management at this time.
As a stop-gap solution, would it be possible to bring back Amarok 1.4.10
as an alternative/parallel install in Jaunty?
** Affects: amarok (Ubuntu)
Importance: Undecided
Status: New
--
Amarok 2 lost support for iPhone-like devices - Choice between 2 and 1.4?
https://bugs.launchpad.net/bugs/362182
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to amarok in ubuntu.
More information about the kubuntu-bugs
mailing list