Re: Cannot mount Galaxy S3 any more

2013-02-12 Thread Ankur Sinha
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

Re: Cannot mount Galaxy S3 any more

2013-02-12 Thread Jonathan Kamens
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 -- test mailing list test@lists.fedoraproject.org To unsubscribe

Re: Cannot mount Galaxy S3 any more

2013-02-11 Thread Ankur Sinha
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 >

Re: Cannot mount Galaxy S3 any more

2013-02-11 Thread Scott Robbins
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 t

Re: Cannot mount Galaxy S3 any more

2013-02-11 Thread Ankur Sinha
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 fi

Re: Cannot mount Galaxy S3 any more

2013-02-11 Thread Scott Robbins
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 P

Cannot mount Galaxy S3 any more

2013-02-11 Thread Ankur Sinha
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:

Re: S3

2011-06-24 Thread Adam Jackson
On 6/24/11 5:49 AM, Rick Leir wrote: > I just installed f15 via BFO, onto a system with S3 PCI video. > By default, the Xorg X11 S3 video driver is not installed. Was this > intentional or should I file a bug? The S3 card is old, but I want my > server to use less power. If you do

Re: S3

2011-06-24 Thread Patrick O'Callaghan
On Fri, 2011-06-24 at 05:49 -0400, Rick Leir wrote: > I just installed f15 via BFO, onto a system with S3 PCI video. > By default, the Xorg X11 S3 video driver is not installed. Was this > intentional or should I file a bug? The S3 card is old, but I want my > server to use less po

S3

2011-06-24 Thread Rick Leir
I just installed f15 via BFO, onto a system with S3 PCI video. By default, the Xorg X11 S3 video driver is not installed. Was this intentional or should I file a bug? The S3 card is old, but I want my server to use less power. It is possible though difficult to use Add/Remove software to add