> Sorry, I meant Canonical people. Canonical is not Ubuntu, even if Canonical is spending quite some resources improving Ubuntu. Canonical is selling support though so if you really need to see that issue resolved you might want consider talking to them about buying support
> I forgot that Ubuntu is supposedly a "community distribution", except when it's not :-p Keep the trolls for another place thanks > Where's "upstream"? Is there a bug tracker for the gvfs people anywhere? https://bugzilla.gnome.org/enter_bug.cgi?product=gvfs > Please understand, the reason this is a confusing issue is that it's not > immediately apparent from any system feedback where the issue lies: Nautilus > pops up on connecting your device, giving a cryptic error from DBUS with very > little help. > Like any non-trivial system where only a small fraction is visible, we must > rely on experts to point us in the right direction. Right, it means it needs debugging from somebody who has a clue about this stack, launchpad might not best the best place, as said Ubuntu is distrubuting this code, not writting it > I understand it's a low priority for Canonical to fix this: maybe changing the error message to "Device not supported" might be more helpful? What is revelant to Canonical doesn't really matter here. Ubuntu is its own project, any Ubuntu member, upstream or community member can be fixing this bug, it's not because Canonical is a big contributor that it's the only one. The issue is also not a priority one but a resources,work ratio one -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/972311 Title: Accessing a MTP device like the Galaxy Nexus fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/972311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
