Broken Alias

[GoogleCodeExporter]

What steps will reproduce the problem?
1. mounts with no errors using gmount
2. Will only successfully mount to /Volumes/foldername
3. When trying to access mount point (/Volumes/gdocs) I receive the error about 
a broken alias, 
the original item could not be found. with options to fix alias, delete alias, 
and an OK button

What is the expected output? What do you see instead?
mounted google documents volume. error described above.

What version of the product are you using? On what operating system?
tried latest macfuse and latest beta, 10.5.6 latest updates, tried with python 
2.5 and 2.6.2

Please provide any additional information below.

Original issue reported on code.google.com by joeyfoxe...@gmail.com on 22 Apr 2009 at 6:32

[GoogleCodeExporter]

Hi, thanks for the feedback. I don't have a Mac to test this on as yet. I'll 
try and
borrow a friend's to look at this as soon as possible. In the meantime, could 
you
please run this file system by running gFile.py directly:
gFile.py email password mountpoint -d
This should cause debug output to be printed to the current terminal. You will 
then
need to use a separate terminal or the GUI to access the mountpoint. Could you 
post
all the debug output up to and including the attempt to read the directory? This
should hopefully give me some information as to what is happening.
Thanks
Scott W

Original comment by d38dm8nw81k1ng@gmail.com on 23 Apr 2009 at 10:28

• Added labels: OpSys-OSX, Usability

[GoogleCodeExporter]

attached. I mounted it the way u listed and accessed the mountpoint in terminal 
and in GUi a few times and 
tried to copy a file.

when trying mounting it this way, I do not get the same broken alias error. I 
can click or cd to the mountpoint 
and see nothing in it. When trying to copy a doc into it, it says not enough 
space.

hope it helps

EDIT: thought that it was strange I didn't get the same error. So I mounted it 
using gmount and tried to access 
it and I do not get the error, but, as before with the gfile.py mount, I still 
cannot read or write to it.

Original comment by joeyfoxe...@gmail.com on 23 Apr 2009 at 2:55

Attachments:

• gdocsdegub.txt

[GoogleCodeExporter]

Thanks. Currently I've not added support for creating new files, which is the 
reason
for your copy error. I will have support for that finished by the end of 
tomorrow
(the first "official" release). The problem is related to files that OS X 
insists on
creating in new directories. I will look at how I can prevent this from 
happening (or
at least fooling OS X in to thinking it is happening). Similar things happen in 
GNOME
on Ubuntu (it tries to create a .Trash file/folder which I haven't 
implemented). It
seems that this is causing more critical errors in OS X than is happening in 
GNOME
and this is causing the problem. Perhaps it'll go away when I add the file 
creation
functionality. If it doesn't, I'll borrow someone's Mac and make it work (by 
brute
force if necessary). I'll keep you up to date with what's happening. I'll list 
this
as accepted and make a start on it ASAP.

Thanks,
Scott W

Original comment by d38dm8nw81k1ng@gmail.com on 23 Apr 2009 at 4:35

• Changed state: Accepted

[GoogleCodeExporter]

Awesome.

Original comment by joeyfoxe...@gmail.com on 23 Apr 2009 at 4:45

[GoogleCodeExporter]

I've finished the basic features and uploaded them last night so my time is now 
free
to work on porting the file system over to OS X. I'll be getting access to a 
friend's
Mac on Monday, so I'll begin work then and I'll hopefully have something done 
by the
end of next week.

Original comment by d38dm8nw81k1ng@gmail.com on 25 Apr 2009 at 1:27

[GoogleCodeExporter]

any updates?

Original comment by joeyfoxe...@gmail.com on 10 May 2009 at 6:08

[GoogleCodeExporter]

Sorry mate, I've been totally bogged down in university assignments so I've had 
no
time to look at the file system since I uploaded the last beta.
I've had a problem migrating it to Ubuntu 9.04 (namely OOo3 breaks it) but if I 
can
fix that problem I believe that it will have me quite a way towards fixing your 
Mac
problem as well. Both issues are related in the sense that they rely on 
accessing
hidden files. My idea is to create these files on the disk but block them from 
being
uploaded to Google Docs. I was going to use the preceding '.' in the names to
differentiate them from other files.
Unfortunately, fixing this OOo3 issue is akin to banging my head against a brick
wall, because it seems designed to make my life difficult.
Anyway, this is my last assignment then I've got a few weeks before my exams so 
I'll
be looking over these issues to see if I can come up with something to fix the
problem and upload when I can.
Thanks for your patience,
Scott W

Original comment by d38dm8nw81k1ng@gmail.com on 10 May 2009 at 7:13

[GoogleCodeExporter]

I assuming this has been put on the back burner for now?

Original comment by joeyfoxe...@gmail.com on 1 Jul 2009 at 11:42

[GoogleCodeExporter]

At the minute. I can't get a hold of a Mac for testing, unfortunately. As soon 
as I do I'll make this top 
priority.
Is the same problem still occurring with the latest beta? 

Original comment by d38dm8nw81k1ng@gmail.com on 1 Jul 2009 at 11:48

[GoogleCodeExporter]

I am on a new install and am having trouble getting everything installed. I had 
to play around with stuff to get it 
installed last time, just cant remember what I did haha. lots of terminal stuff 
and i get lost haha

Original comment by joeyfoxe...@gmail.com on 2 Jul 2009 at 3:16

[GoogleCodeExporter]

Aha. Its good to hear that it can be made to work. If you can do it again, 
could you post it here and I can 
put the info in the manual, or try and figure out how to automate it. Cheers.
Scott W

Original comment by d38dm8nw81k1ng@gmail.com on 2 Jul 2009 at 7:18

[GoogleCodeExporter]

Does google-docs-fs support now creating new files in Mac OS X ?
Thank you for your job

Original comment by jbrechbu...@gmail.com on 16 Jan 2010 at 12:51

[GoogleCodeExporter]

Honestly, I don't know. I don't have a Mac to do any testing on so I'm reliant 
on
people reporting and fixing issues before relaying this information on. There 
is code
that is intended to fix or workaround OSX specific issues but it's mostly 
guesswork.

Original comment by d38dm8nw81k1ng@gmail.com on 16 Jan 2010 at 3:46

[GoogleCodeExporter]

OK. I have Mac OS X, maybe I can help you. I mounted my google docs 
successfully, I
can see my files. But I can't open them, mac os say I don't have the 
permission. But
if I read file properties, I can see I have read/write permission like on the
properties of the MacFUSE Volume.

Original comment by jbrechbu...@gmail.com on 16 Jan 2010 at 6:54

[GoogleCodeExporter]

I've just received an error report under Issue 15. Perhaps this could be the 
cause?
If possible, could you run with the debug flag and see if the problem is the 
same one?
Cheers,
Scott W

Original comment by d38dm8nw81k1ng@gmail.com on 18 Jan 2010 at 8:55

[GoogleCodeExporter]

I think I have the same error report like Issue 15. I posted a debug file, I am 
not
sure. I did few tests: mount, ls -l, view (vi) a file, and touch a file. 

Original comment by jbrechbu...@gmail.com on 19 Jan 2010 at 7:44

Attachments:

• log_google-docs-fs.rtf

[GoogleCodeExporter]

I'm going to assume the change I've made have fixed this. If this reoccurs feel 
free
to comment on it.

Original comment by d38dm8nw81k1ng@gmail.com on 6 Mar 2010 at 11:25

• Changed state: Fixed