Previous 1 2 3 Next 37 Replies Latest reply: May 14, 2012 12:11 PM by Cattus Thraex Go to original post Branched to a new discussion.
  • isbyrne Level 1 (0 points)

    Try This:


    To make your Library folder permanently visible, follow these steps:

    1. Launch Terminal from the /Applications/Utilities folder.
    2. Type this single line and press return to make the Finder visible again. This assumes you are logged into the account in which you want the Library to become visible:
    chflags nohidden ~/Library

    Now you should be able to see the Library folder from within your user folder.

  • gumsie Level 4 (2,155 points)

    You're running Lion?

    The Top level Library should be visible and is at the follwing path;


    The User Library will be at;



    You should be able to get to them in the Finder by either a). Navigating through or b). copying the above text of whichever you want to get to and pasting it into the window that pops up when you press Command-Shift-G.

  • Royden Kading Level 1 (60 points)

    Happy New Year.

    Thanks finally got to the Library and logs.  I have been reading through them but honestly don't understand them. 


    I haven't activated iCloud on the Mac Book yet.  Will do that. 


    The Mac Book has the same apps, files, etc as my desktop.  On both we use Mail and Safari, so can't understand why this is happening.  Will keep looking and testing.

    Thanks for all your help.

  • gumsie Level 4 (2,155 points)

    No problem. What you need to do is copy and paste the Safari crash log.

    It'll start with a line that says something like;

    Process : Safari [7534.52.7]


    Somebody clever will be along to diagnose......

  • isbyrne Level 1 (0 points)

    Hi folks,


    I seem to have solved my freezing issues but unfortunately I am not sure how.


    I removed all powerpc files and also went through the libraries and manually removed all remaining help files etc from old or trial software.


    I then discovered that my itunes library was corrupt so I restored it from a time machine backup, this worked fine.


    I suspect the intiial problems may have been caused by a corrupt file but cannot verify this.

  • macieksmuga Level 1 (0 points)

    Hi all,


    I've been experiencing similar issues on my mid-2010 MacBook Pro 15'', ever since I upgraded to... 10.7.1 (or was it 10.7.2)?


    The last message in the /var/log/system.log before the machine becomes unusable is always an invocation to backupd, the backup daemon that I presume is used by Time Machine.


    At which point, the file system deadlocks on write access.


    (I verify this by running a simple command on the terminal that requires file system write access, like "touch ~/foo" and seeing if it ever returns) So: Of course there are no further log entries of what may have gone wrong (after all, you can't write to a log if file system write is blocked).


    To sow further confusion, other currently open apps _seem_ to continue working right up until they need to write something to disk (reading from disk is fine, as are all other aspects of the OS as far as I can tell).


    The infuriating thing is that this is intermittent: Sometimes Time Machine does its thing just fine. Others, it freezes as described above and the ONLY thing I can then do is a hard reset.

  • billegates Level 1 (0 points)

    I have the same problem. I am going to try a clean install of Lion today.

    If I get "no joy" from that, I will try to reinstall 10.6



  • Cattus Thraex Level 4 (1,715 points)

    The overwhelming majority of Lion issues are due to taking over older, outdated apps, which start up at login or intefere with the system. The same occurred with practically all new generations of Mac OS X. The issue is perhaps more frequently with Lion, because default installation of Lion is to upgrade SL, but not other apps, of course. Upgrading has its advantages, of course, nevertheless may have negative results. All may be better if Apple introduced a script to deactivate all non-Apple apps starting up at login to be later activated under a certain control. In most cases, creating a new user, loging out and reloging into the new system proves that all is OK.

Previous 1 2 3 Next