Closing due to age and lack of activity.
If a similar bug appears in 13.10 please open a new report.
** Changed in: gvfs (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.laun
[Expired for libmtp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libmtp (Ubuntu)
Status: Incomplete => Expired
--
DBus error when connecting my Sansa E260
https://bugs.launchpad.net/bugs/247312
You received this bug notification because you are a member of Ubun
It seems to work fine for me on Karmic now, but I see two devices in
nautilus when browsing computer:///, "SanDisk Sansa e250" and "SanDisk
Sansa e250: SD PLAYER". Trying to use the former just results in an
error "Unable to mount location: no media in the drive" but the second
one takes me to /med
The Sansa E260 is included in the list of libmtp's supported players, at
least on Karmic. The player's ID is already in the version included with
Jaunty, but is named the Sansa E280 v2 there; the Sansa E260 and the
Sansa E280 v2 share the same ID.
Can you confirm that this bug still exists? Otherw
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Package changed: nautilus (U
Doesn't look like a D-Bus issue
** Package changed: dbus (Ubuntu) => nautilus (Ubuntu)
--
DBus error when connecting my Sansa E260
https://bugs.launchpad.net/bugs/247312
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
