Hi folks,
Of late, my up to date F18 system doesn't show my galaxy s3. lsusb seems to find it: Bus 002 Device 017: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
dmesg keeps giving errors like this: http://paste.fedoraproject.org/2769/
There doesn't seem to be any /dev/serial*:
[root@dhcppc1 ~]# ls /dev/ser* ls: cannot access /dev/ser*: No such file or directory [root@dhcppc1 ~]#
mtpfs fails with the following output: http://paste.fedoraproject.org/2770/
Would any one know what's causing this and whether a bug is filed (and against what component?)? I'll go file one other wise. It's basic functionality that should be available. At the moment, I can't import photos from my phone to my system :/
(I had a Jellybean update to 4.1.2 recently but googling doesn't give me much information on whether it broke mtp etc.)
On Tue, Feb 12, 2013 at 12:46:18AM +1100, Ankur Sinha wrote:
Hi folks,
Of late, my up to date F18 system doesn't show my galaxy s3. lsusb seems to find it: Bus 002 Device 017: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
Up to date F18 system mounts 4.1.1, using simple mtpfs (all done by command line, no auto mounting) without issue.
Haven't upgraded to 4.1.2.
On Mon, 2013-02-11 at 09:19 -0500, Scott Robbins wrote:
Up to date F18 system mounts 4.1.1, using simple mtpfs (all done by command line, no auto mounting) without issue.
Haven't upgraded to 4.1.2.
I just tried simple-mtpfs and it works. I'm not sure what broke the automount. dmesg finally says:
[85622.198066] systemd-udevd[20932]: Failed to set security context (null) for /dev/serial/by-id: File exists [85622.198167] systemd-udevd[20932]: Failed to set security context (null) for /dev/serial/by-id: File exists [85622.198270] systemd-udevd[20932]: Failed to set security context (null) for /dev/serial/by-id: File exists [85622.198409] systemd-udevd[326]: worker [20932] /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1/tty/ttyACM0 timeout; kill it [85622.198427] systemd-udevd[326]: seq 2644 '/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1/tty/ttyACM0' killed
I filed a bug against mtpfs:
https://bugzilla.redhat.com/show_bug.cgi?id=910207
On Tue, Feb 12, 2013 at 12:39:33PM +1100, Ankur Sinha wrote:
On Mon, 2013-02-11 at 09:19 -0500, Scott Robbins wrote:
Up to date F18 system mounts 4.1.1, using simple mtpfs (all done by command line, no auto mounting) without issue.
Haven't upgraded to 4.1.2.
I just tried simple-mtpfs and it works.
I filed a bug against mtpfs:
It'll probably be closed as won't fix. I think---DISCLAIMER--I could be wrong, but I'm almost certain that I've seen a bug report and the final decision was to let it go and use simple-mtpfs and/or jmptfs. The reason was, (again, memory may be faulty) that upstream is pretty abandoning it in favor of simple and/or j.
I repeat, my memory could be off on this, but I'm fairly sure that's the case.
Anyway, glad you got your particular sitaution fixed.
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Hi Scott,
On Mon, 2013-02-11 at 22:22 -0500, Scott Robbins wrote:
It'll probably be closed as won't fix. I think---DISCLAIMER--I could be wrong, but I'm almost certain that I've seen a bug report and the final decision was to let it go and use simple-mtpfs and/or jmptfs. The reason was, (again, memory may be faulty) that upstream is pretty abandoning it in favor of simple and/or j.
I repeat, my memory could be off on this, but I'm fairly sure that's the case.
Yep. The package is orphaned so I'm pretty sure the bug won't be fixed. I filed it in case anyone else experiences the same issue and decides to go hunting, like I did.
Anyway, glad you got your particular sitaution fixed.
Me too. :)
I've mailed the desktop list asking them if they know how MTP and auto-mounting in Gnome3 is supposed to work. Let's see what they have to say.
I have a Galaxy SIII running Android 4.1.1 (the standard Verizon Wireless image, not rooted) and Nautilus in F18 is able to mount it and access its files just fine as long as I make sure it is unlocked before I plug it in.
jik
On Tue, 2013-02-12 at 09:19 -0500, Jonathan Kamens wrote:
I have a Galaxy SIII running Android 4.1.1 (the standard Verizon Wireless image, not rooted) and Nautilus in F18 is able to mount it and access its files just fine as long as I make sure it is unlocked before I plug it in.
Ah! Then it could probably be Android 4.1.2 breaking something. I'm using the default Optus image too, phone isn't rooted yet.
The folks over at the desktop list mentioned that mtp support has been added to gvfs and will land in gnome 3.7.5, so F19. I'll see how that goes.