Have to create new user account to run L4
I saw the thread regarding this a while back, but didn't see it come to any resolution. I've having the same problem. Any updates on this?
Comments
-
Could you link to the thread?
0 -
Could you provide some more detail regarding what you're asking for, or (better yet) post in the original thread so that it is easier to understand the context of what you're asking?
David Mitchell
Development Lead
Faithlife0 -
Here's the original thread:
0 -
There's very little that we can do to diagnose problems that users are having without logs (or physical access to a computer exhibiting the problems), and we never received them from the user who reported that problem.
If you would like to post your logs, we may be able to help you out. Instructions for doing so are in the FAQ at the top of the forum.
David Mitchell
Development Lead
Faithlife0 -
I will post the logs. My only concern is that I have no logs on the primary user account that I work in on my mac because it won't run from that user. I can print out the logs from the new user account profile I created because it works fine there. I'm just afraid there will be nothing to diagnose in those logs because it is operating fine within that account. Hope that makes sense. I will post the logs in a few. Thanks.
0 -
This might be a better way to say what I was trying to say in the last post.
On my original user account on my mac, I am unable to run Logos 4 (but I am able to run 3). Therefore, I have no Logos4 folder in my Library/Applications Support folder nor is there any Logos related folder in the Library/LaunchAgents folder.
This is not the case with the new user account I created because it runs fine in that user account.
I will still post the logs that I do have.
0 -
-
Could you try using it in the user account in which Logos 4 doesn't work and post just your Console Log (which isn't stored in the Logos4 directory)?
David Mitchell
Development Lead
Faithlife0 -
I think this is what you're looking for. If not I can try again.
0 -
That's exactly what we need.
There's an error in your log that I've never before seen. We should be able to track it down.
David Mitchell
Development Lead
Faithlife0 -
I'm not certain if it will work, but try this:
Open Terminal
At the prompt, type "ls -ld ~/.wapi" (without the quotes). Press enter.
Copy the output and paste it into a forum post (this will help us fix it automatically for other users if this is the solution)
At the prompt, type "chmod -R 755 ~/.wapi" (again, without the quotes). Press enter.
Try running Logos 4.
Tell us how it works (and if it doesn't work, post your console messages again).
David Mitchell
Development Lead
Faithlife0 -
Here is the output for ls -ld ~/.wapi:
ls: /Users/jal/.wapi: No such file or directory
0 -
Here is the output for chmod...
chmod: /Users/jal/.wapi: No such file or directory
0 -
Didn't work. Same stall and never launches. Here is the latest console log:
0 -
Joel Lindsey said:
Didn't work. Same stall and never launches. Here is the latest console log:
OK. Try the following 2 commands from Terminal then restart Logos 4.
mkdir ~/.wapi
chmod 755 ~/.wapi
Mobile Development Team Lead
0 -
Log is attached
Here are the terminal results
Joel-Lindseys-MacBook-Pro:~ jal$ mkdir ~/.wapi
mkdir: /Users/jal/.wapi: Permission denied
Joel-Lindseys-MacBook-Pro:~ jal$ chmod 755 ~/.wapi
chmod: /Users/jal/.wapi: No such file or directory0 -
Run the mkdir command again but place "sudo" without quotes in front of it. OS X will ask for your password. Enter password and the command should execute.
0 -
Hmmm... Seems like the permissions on your home directory are messed up.
Try the following commands from Terminal and post the results. Don't bother re-running Logos 4 after this as these are just diagnostic.
ls -ld ~
ls -ld ~/Documents
Mobile Development Team Lead
0 -
MichaelKares said:
Run the mkdir command again but place "sudo" without quotes in front of it. OS X will ask for your password. Enter password and the command should execute.
Actually, you probably don't want to do this as it will create the directory as owned by the root user, and you won't be able to write to it, which is the situation you find yourself in now.
If you've already done that, you might need to do "rm -r .wapi" (without quotes). Answer y when prompted. Hit enter.
Mobile Development Team Lead
0 -
Michael, this is the output from the sudo command
Password:
Joel-Lindseys-MacBook-Pro:~ jal$ sudo mkdir ~/.wap
mkdir: /Users/jal/.wap: File exists0 -
My bad. Figured it would grant him root access to create the directory under his home folder. I'll just stay out of the way [:P]
0 -
You are better off listening to Tom's advice. Most of my experiments with Terminal were following instructions on Google. And I was a little bummed when OS X shut down that "fork bomb". I wanted to see what would happen......[8-|]
0 -
I ran the sudo command already. Tom, I tried your suggestion and this is the output I got:
Joel-Lindseys-MacBook-Pro:~ jal$ rm -r .wapi
rm: .wapi: No such file or directoryShould I still run the previous suggestion (below):
ls -ld ~
ls -ld ~/Documents
0 -
Yes. Please do.
Mobile Development Team Lead
0 -
Here is the output:
Joel-Lindseys-MacBook-Pro:~ jal$ ls -ld ~
drwxr-xr-x 19 joellindsey staff 646 Apr 20 22:31 /Users/jal
Joel-Lindseys-MacBook-Pro:~ jal$ ls -ld ~/Documents
drwx------ 10 jal staff 340 Aug 4 2009 /Users/jal/Documents
Joel-Lindseys-MacBook-Pro:~ jal$0 -
Oh... There's your problem... You must have copied your home folder over from another account. You are currently logged in as "jal" but your home folder is owned by "joellindsey". Which is why you can't create the .wapi folder.
Here's the fix from Terminal type the following and enter your password when requested.
sudo chown jal:staff /Users/jal
To verify that it worked:
ls -ld ~
Then restart Logos 4.
Mobile Development Team Lead
0 -
SUCCESS!!!!!!!!!!!!
Thanks a ton, Tom. You just made me a heck of a lot more productive. Hope you guys benefit from this in some way as well.
0 -
Joel Lindsey said:
SUCCESS!!!!!!!!!!!!
Thanks a ton, Tom. You just made me a heck of a lot more productive. Hope you guys benefit from this in some way as well.
Besides the fact that you're up and running, we now know of one other way that the app can fail due to an environment configuration issue. We'll see if we can come up with a programmatic work around (or at least some logging to point us the the root cause faster).
Mobile Development Team Lead
0
