i have the problem ubuntu system 18.4.
how to disable mtp device on ubuntu system .( Mobile device all Model)
how to disable
pls help
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
need help this is what im getting as im running ubuntu 14.04 "Unable to open
~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 16
Comment #40 (the two killall commands) did it for me on 14.04.5 64-bits
desktop with a Samsung Note 3. THANKS!
--
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/1314556
Title:
Unable to
Ruslan (#80) solution worked also for me:
- amarok MTP plugin disabled
- amarok restarted
- it is now working
As Stephen, I'm not KDE user (Xubuntu) but I use amarok always in
systray ;)
It would be nice to fix amarok mtp plugin.
Many thanks for the workaround :-D
--
You received this bug
Ruslan (#80) solution worked for me:
"For KDE users experiencing a similar issue, make sure that either
Amarok isn't running or its MTP plugin is disabled."
I am not a KDE user, but I was running Amarok - listening to it while I
tried to sort-out my 'phone.
It lives in my system-tray
I can confirm that killing gvfs-gphoto2-volume-monitor fixed the problem
in Ubuntu 16 with all my Android devices.
--
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/1314556
Title:
This has been happening to me since I upgraded to 17.04 developer
preview. As soon as I run Ubuntu in VirtualBox (either 16.10 or 17.04
guest and 17.04 host) and redirect Android phone to it, the system goes
wild. Files in /var/log on the host grow to occupy the whole space, all
memory is also
Same problem. Intermittent, but for the last few days doesn't work. I
have attached the output of numerous cli commands to help
troubleshooting. When I choose PTP mode instead of MTP mode Shotwell
fires up and can receive photos and videos.
One thought is that USB cables are notorious for wearing
I had a similar problem show up on Lubuntu 16.04 (i386). One thing that
SEEMS to work (it actually made a Samsung phone reboot!) is
1) disable the "USB debugging" on the phone;
2) set the phone to Airplane mode (so it doesn't try to make a network
connection).
In my case, running `dmesg` it
I was ripping my hair out with this one. All the suggestions above not
working for me. Phone is Samsung S5.
ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
So I tried (from terminal) "killall nautilus", then restarted it (by
clicking on file icon). "Samsung ANDROID" now shows up in
MTP access is broken
Galaxy Note 7 (6.0.1) with 256GB card connected to Kubuntu 16.04 with kernel
4.7.2, same with S5 with 64GB card and S3
Phones are set to developer mode
USB set to File Transfer
Amarok is not installed.
Dolphin will connect, but it's intermittent.
If a connection is made it
Having the same issue on Elementary os 0.4 Loki
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this
In general, to begin finding what application takes your Android device,
try the following command:
sudo lsof | grep /usb/
This should give you some pointers to processes using files in e.g.
/dev/bus/usb/.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
For KDE users experiencing a similar issue, make sure that either Amarok
isn't running or its MTP plugin is disabled.
--
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/1314556
Title:
I can't connect my Android phone in 16.04, even worse my Auquaris E4.5
isn't able to connect either. Kinda painful that an Ubuntu phone can't
connect to a computer running Ubuntu. ;P
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Just tried it with 16.04 and my Ubuntu phone, and the problem is still
there... indeed rather embarrassing that my Ubuntu computer can't talk
to my Ubuntu phone. This bug is now two years old by the way.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
It would be more productive to give some more details here.
I had this problem on 15.10 and now 16.04, and other subsystems are
working okay as I am able to connect via ADB. When I try to connect I
get the error message: "No Storages found. Maybe you need to unlock your
device?" The device is
I have the same issue with a nexus 5, and with marshmallow there seems
to be no other option than MTP.
What does the ubuntu phone use? I hope its not MTP because that would
just be embarrassing...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I can confirm this on two computers. One with 15.10 and the other with
14.04 (LTS version). Thing is, gMTP is working fine out of the box on
both computers so the issue is not the hardware.
I have had problems with MTP ever since android switched to MTP (various
phones, various computers) but
Sorry, was too quick. Should add that I have tried various workarounds
with udev rules, the workaround in comment #40 etc, nothing seems to fix
the connection out of the box. I need to rely on gMTP for transfer.
--
You received this bug notification because you are a member of Ubuntu
Desktop
"Me too", with Ubuntu 15.10 and Jolla Sailfish (not Android!).
Workaround in comment #40 works, though you need to run /usr/lib/gvfs
/gvfs-mtp-volume-monitor to detect the phone.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
I'm having the same problem with both my 2012 Nexus 7 and my HTC One M8.
If I connect the device, I get the error message "Unable to mount
Android Phone: Unable to open MTP device '[usb:005,120]'" for my HTC One
M8. The message changes to "Unable to mount Nexus 7" when I plug the
Nexus 7 in. The
I also get this message all the time with my Nexus 5. Typically, I get
the "Unable to mount Android MTP device" error message popping up on my
screen when I plug in my phone, but *not* always. Since I plug/unplug
my phone very often, I typically get 4-5 of these messages hidden behind
windows
I have the same problem with Nokia Lumia 1520. It stays hanged when choosing
the phone. and the similar log output on mtp-detect.
But there is one thing i found out. When i removed cd card (64 GB) from the
phone it started to work as expected. Maybe the problem is with sd card support?
--
You
I tried plugging in to two different USB ports, then repeatedly into
one. It finally took, so the problem is intermittent for me.
It turns out mtp-connect was hanging in a terminal window and I found a
lot of what might be useful debugging info when I went back to it (after
the successful mount):
What I can say is that it never worked for me on Trusty with the 3.13 kernels
and continues to not work with the mainline 4.2.5 kernel.
Which USB port I plug it in does also not matter. Tried USB 3.0 ports on the
back and two of the USB 2.0 ones. No dice. Same for the ones on the front of my
Just a quick comment. I know this was mentioned before (#46) but it
would be a good idea if everyone checked this behaviour with phone in
both locked and unlocked states _before_ it is plugged into the USB.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
also affects me on 14.04 with an samsung galaxy tab 4 running
cyanogenmod11 android 4.4.4
--
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/1314556
Title:
Unable to mount Android MTP
Actually, as an experiment, I did a restore to a week old Clonezilla
image, and MTP even worked on that one for me. But I don't recall MTP
ever working for me on 14.04. Weird. Anyway, it works now, so who cares.
Also, I was wrong about the kernel thing, they haven't downgraded
anything.
--
You
Damn, it stopped working again. Ubuntu 14.04. It worked for a little
while, don't know why. Which USB port I use makes no difference.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Change to USB 3.0 Port
work laptop and desktop.
(Desktop usb 3.0 is back of system box, laptop 3.0 is blue or ss <-
--
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/1314556
Title:
There was just an official update from Canonical for my 14.04 LTE. MTP
with my Android device now works flawlessly. It looks like they have
downgraded the kernel. I ran "uname -r" and it seems the kernel is now
"3.13.0-65-generic." I'm happy it works now.
--
You received this bug notification
Same problem on 15.04 with an HTC Desire 820. Unable to mount android
phone message and then an empty nautilus browser window. Is this
something to do with the transient usb mass storage device that phones
with this chipset reports on the usb bus for a while after first
connection. This is
Hi guys
This is a pretty serious issue, how has there been several major
releases recently without this basic functionality issue solved?
Has anyone even tried? This is basic functionality for a modern OS.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Tested with mainline kernels
https://wiki.ubuntu.com/Kernel/MainlineBuilds
http://kernel.ubuntu.com/~kernel-ppa/mainline/
On the most recent kernel v4.2-rc8-unstable problem persists (lsusb hangs,
MTP/ADB do NOT work)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc8-unstable/
On kernel
Ok, I have found a workaround solution, at least for my case - just
downgrade the kernel to 3.16 (default version on 14.04 is 3.19). With
this kernel lsusb returns result instantly and MTP/ADB work reliably,
nautilus shows Android on connect/reconnect immediately, ADB shows
device and does not
Even more funny, with kernel 3.17 Firefox stopped hanging the on the
page I have linked above http://www.howtogeek.com/196655/how-to-
configure-the-grub2-boot-loaders-settings/ (on kernels starting from
3.18-rc1 the whole application would hang after few seconds during
loading this page).
This
I have a bit more info here. I have Ubuntu 14.04 (15.04 all the same)
running on HP Envy m6 laptop + Android YotaPhone1 and have all listed
problems with MTP/ADB here: the connection is unreliable (works 1 of 10
or does not work at all). None of the suggested solutions (using mtp
tools or killing
some output from Ubuntu 14.04 on Hp Envy m6 (MTP/ADB does not work):
uname -a
lsmod
may be useful to compare with OpenSUSE 13.2 output on same hardware (MTP
works) from the comment above.
** Attachment added: Ubuntu 14.04 on Hp Envy m6 (MTP/ADB does not work)
+1 on the last comment.
Personally I think it's a shame for the Linux world, that such a show
stopper is not fixed since 2 major releases! How should I convince
anyone having a non Mass-Storage Smartphone to switch to Linux??? These
errors occurred on plain installs from the DVD-Images.
I wonder
+1 on the last comment.
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this bug go to:
Same issue with 15.04 LTS and libmtp 1.1.8
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this bug go
I was having this problem with a Sansa Clip Zip. I changed USB mode (on
the Sansa's settings) from MTP to MSC and now the Sansa is mounted just
fine and shows up as a mass storage device.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Similar problem with a Samsung NT5110, in an unstable state. That is
it starts up, partially, and displays the reboot..factory reset.. clear
cache menu.
Samsung will do a depot rebuild for $160 US. Thus, my attempt to
reinstall from a Linux/Ubuntu 14.04 system. I do not have a keyboard
for
If I plug the phone to ubuntu 14.04 i386 desktop PC, it will work.
If I plug the same phone to ubuntu 14.04 64bit laptop, it will NOT work.
Damn weird.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
steps:
1. adb root
2. Then, it will popup unable to mount android: Unable to open MTP device
'[usb:001,123]'
3. if you unplug, then replug it's OK again.
** Attachment added: unable to mount android: Unable to open MTP device
'[usb:001,123]'
My Nexus 4 is unlocked when Ubuntu fails to mount Android MTP device.
Jim S.
On Saturday, May 30, 2015 9:10 AM, Garry Cairns
1314...@bugs.launchpad.net wrote:
Can I just check that all the people here reporting phone issues have
unlocked the phones? For example, if you need to
Can I just check that all the people here reporting phone issues have
unlocked the phones? For example, if you need to enter a passcode or
draw a shape to use your phone, it also won't let a computer access it
until you enter the same code to unlock the phone. That's a feature of
the phone rather
I seem to have the same problem with MTP and a Nokia Lumia device
wunning WP 8.1
--
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/1314556
Title:
Unable to mount Android MTP device
To
ubuntu 14.04 with samsung galaxy note 3
mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 3, dev
I'm now on Kubuntu 15.04, and the problem still exist. In my case
turning on USB debug in advanced options helped... but it shouldn't be
that way.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Killing gvfs-gphoto2-volume-monitor and gvfs-mtp-volume-monitor as
Andres pointed out worked for me too.
--
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/1314556
Title:
Unable to mount
For me, the fix was to use a USB port on the back of my machine direclty
on the mother board.
--
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/1314556
Title:
Unable to mount Android
Also affected. In my case, a Samsung Galaxy S SCL GT-I9003
Ubuntu 14.04 ships libmtp 1.1.6. I wonder if a higher, or lower version
of this lib, would fix these problems? (I said lower in my previous
sentence, because many people claim here that it worked with Ubuntu
12.04.)
Apparently Ubuntu
So I've found a workaround. In a terminal, do:
$ killall gvfs-gphoto2-volume-monitor
$ killall gvfs-mtp-volume-monitor
Then reconnect your device. Now mtp-detect works, and other players that
use libmtp.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Interestingly enough, I removed all my mtp packages, and installed
libmtp-code from the git's source (tried both 1.1.8 and 1.1.6) and it
made suddenly mtp-detect to start working (in both versions).
So I'm wondering what to do next, to keep on pinpointing the problem.
--
You received this bug
note: rebooting the computer (!) seems to help.
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this
Hi all,
waht is the situation today ? i have this bug since i update my ubuntu to 14.04.
do This bug is resolved with the new update 15.04 ?
thanks a lot
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Ubuntu 14.04 64-bit: I find that the Nexus 5 connects intermittently,
whereas the Samsung (two different models) won't connect at all.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Affects me as well: Ubuntu 14.04 and Galaxy S3. Toggling USB debugging
off and back on again had no effect.
--
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/1314556
Title:
Unable to
Earlier this week - probably Monday (Jan-19-2014), I was able to mount
my Samsung NotePro 12.2 and copy my music to it. Friday (Jan-23-2014), I
am not able to. I think this was due to some upgrades.
I'm not sure what additional information you need, so please let me know
and I will be happy to
@protagoras: Unfortunately, jmtpfs also doesn't work for me. jmtpfs
~/mtp just gives me:
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb:
I am also affected. Samsung S4, Ubuntu 14.04.
Odd pattern: I turn phone USB Debugging off, then on again -- the phone
shows up for perhaps 10 seconds and I can run around the (limited)
directories within Nautilus. Then I get the error '
mtp:host=%5Busb%3A003%2C024%5D” could not be found. Perhaps
I experience the same issue with Ubuntu 14.04 LTS and a Wiko Bloom with
Android 4.4.2. What kind of information do you need in order to debug
this?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
I've experienced this issue with a Galaxy S4 running 4.1 and now a
Galaxy Note 4 running 4.4.4.
--
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/1314556
Title:
Unable to mount Android
I also can't connect my LG G2 not recognized at all even with command [
ls /dev/sd* ] in terminal under usb 2.0 or 3.0 under MTP. If i use PTP i
can only see [pictures] and [DCIM] folders and there content. I am
trying to use ubuntu to fix my phone and unless this is fixed it isn't
going to
Ubuntu 14.04.1 LTS
Samsung Galaxy S4
'Unable to open MTP device'
Worked fine on Xubuntu 14.10
--
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/1314556
Title:
Unable to mount Android
Have you tried with jmtpfs? It works like a charm for me. E.g., from a
terminal window:
mkdir ~/mtp
jmtpfs ~/mtp
ls ~/mtp
fusermount -u ~/mtp
https://github.com/kiorky/jmtpfs
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
[Edit] Several models reported here (Samsung Galaxy [S2], Sansa [View,
e260]) should work with libmtp (and hence with jmtpfs), as they are
explicitly mentioned in the configuration file of the library;
https://sourceforge.net/p/libmtp/code/ci/HEAD/tree/src/music-players.h
--
You received this
This also affects Trisquel 7.
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this bug go to:
I have the same issue.
I use:
- Ubuntu 14.04.1 LTS
- Example device that does not work: Samsung Galaxy S2, Android 2.3.6
Environment: Device was connected to USB Hub and then to Ubuntu machine.
I observed that:
- Device icon is visible on Ubuntu desktop.
But when I click that then I cannot go
I have the same problem. But I am able to get it to mount after plugging
the phone in, going to Settings - Developer Options and turning off USB
Debuggling and turning it back on again (Hello IT, have you tried
turning it off and on again?).
-
agentlogic@Erebus:~$ mtp-detect
I am unable to mount Nexus5 and Samsung Galaxy 2 on Ubuntu 14.04
I was able to do file operations without any issues in prior versions.
Following is the output that I got when tried for mtp-detect.
-
xanthus@xanthus-Inspiron-6000:/etc$ mtp-detect
Unable to open ~/.mtpz-data for reading,
Same problem with a Sansa e260:
Bus 001 Device 007: ID 0781:7420 SanDisk Corp. Sansa E200 series (mtp)
--
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/1314556
Title:
Unable to mount
Hi, This bug also affects me on ubuntu 14.04, whether I am on USB debugging
mode or not on my Xperia M2.
The phone detects the PC connection and tells me it is connected in MTP mode.
However nothing happens on the computer. When I try mtp-detect :
Unable to open ~/.mtpz-data for reading, MTPZ
Sorry, another thing : the device is detected using command lsusb :
Bus 002 Device 023: ID 0fce:51aa Sony Ericsson Mobile Communications AB
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Looks to be similar output without usb debugging.
** Attachment added: Output_without_usb_debugging.txt
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+attachment/4200267/+files/Output_without_usb_debugging.txt
--
You received this bug notification because you are a member of
I see that my Galaxy S4 mounts and I can see the file names on the phone
and on the SD card but I can't access them. When I run mtp-detect with
usb debugging set to ON I get the following output.
** Attachment added: Output_with_usb_debugging.txt
** Changed in: gvfs (Ubuntu)
Importance: Low = High
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about
affects me too.
kengyu:~ $ mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=1bbb and PID=0168) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
1bbb:0168
This affects me too.
$ mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 6
Attempting to
Unable to open MTP device '[usb:001,023]'
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this bug go
It's not only Android devices having a problem mounting MTP devices in
Ubuntu 14.04. I have a Sansa View player that will not mount. The Icon
comes up on the vertical side panel (whatever the heck it's called I
can't remember) - the one with all the icons. If I try to open the
device, it won't
ADDENDUM:
I just plugged my SansaView back into the USB port on my computer while my
phone was plugged in and, Hello!, the thing mounted and I was able to access
the folders. Ah, the mysteries of computers. If they weren't so damn
frustrating, I'd be intrigued.
--
You received this bug
ADDENDUM:
I just plugged my SansaView back into the USB port on my computer while my
phone was plugged in and, Hello!, the thing mounted and I was able to access
the folders. Ah, the mysteries of computers. If they weren't so damn
frustrating, I'd be intrigued.
Turns out the minute I unplug
What's the issue exactly? Is the device detected by the desktop when
connected? Is your problem that the automount lock the device and you
can't access it from a command line then?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs
None of my MTP Android phones are detected by the desktop at all, worked
perfectly in 12.04.
Sony Xperia ZR for example.
--
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/1314556
Title:
How can this have importance low??
Btw, for me turning on USB debugging does NOT fix the issue.
--
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/1314556
Title:
Unable to mount Android
I agree with previous commenters, this is a serious problem, it means that MTP
support is broken on Ubuntu which makes it almost impossible to use for Android
development for some of the most common phones and tablets on the market.
And it has been a problem for some time now. It is a high
This seriously affects android developers
--
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/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this bug go
My HTC One running Android 4.2.2 would not mount under Ubuntu 14.04. I
finally figured out that turning on USB debugging on the phone (under
developer options in the settings menu) fixed the issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New = Confirmed
--
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/1314556
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
93 matches
Mail list logo
