Francois Jaouen [2010-03-18 21:47 -0000]:
> "Everything run smoother since this line is commented out."
> 
> I was hacking Rhythmbox in order to use gvfs layer instead of direct
> access to mtp devices when I encountered the problem.  Rb relies on
> mpi files for UMS devices and I plugged MTP devices on the same code
> (so I needed that ID_MEDIA_PLAYER points to the mpi file what
> 90-usb-media-players.rules is supposed to do AFAIU)

Ah, I see. Well, it would certainly be nice if gvfs would also get
along with the player through the libgphoto backend, so that you can
also browse files in nautilus, etc.

Unfortunately I only have a Samsung U5 here, which speaks both UMS and
MTP. So in gvfs/nautilus I see the mount, and if I open RB it unmounts
and uses libmtp.

So if m-t-p knows about an MTP device, I don't see why it would hurt
to set the actual mpi file instead of just "1" (what the libgphoto
rules do).

> Nevertheless I still don't understand the logic of
> 90-usb-media-players.rules.  At first it defines data (ex:
> ID_MEDIA_PLAYER the one I was looking for) for pure MTP devices
> (read no UMS support) but because of SUBSYSTEM!="block",
> GOTO="media_player_end" these data are never read.

Well, 95% of mtp is a direct import of hal-info's music-player
database by now; it's not unlikely that this also contained MTP
players.

> So, it doesn't make any sense to me to correct the first point
> (adding id 4131 for Creative Zen Touch) and not the above test.

Agreed. I'd like to fix the test, too. I'll get to that soon.

> PS : If its not the right place to discuss of udev/m-p-i let me know
> where I can find information.

It's fine. mpi bugs are tracked on bugs.freedesktop.org these days,
but since I'm upstream I don't care much whether it's on fd or LP :)

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

-- 
Creative Zen Touch not properly detected
https://bugs.launchpad.net/bugs/478789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to