Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 32 replies
  • Subscribers 6 subscribers
  • Views 46934 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to complete login after reboot

mdoorkeeper

Hi,

I installed Sophos Anti-virus for Mac Home Edition yesterday.  Install went as expected.  I ran a custom scan on a small micro SD to try it out and it went well, so I ran a full system scan.  That went faster than expected - MUCH faster than ClamXav, so I thought, "I like this".  BUT!!!! When I went to restart my computer today, I was unable to login to my admin account.  The whole computer would hang and become completely unresponsive to any interface just after launching Finder.  I had to force shutdown using the manual button in the top right corner.  I then ran "Applejack", (which cleaned a HUGE cache file), and rebooted.  Same result, ie; hang after Finder launch.  Sooo, I forced shutdown again, rebooted in Safe mode, and uninstalled Sophos AV.  

It has been suggested on another forum that the problem is that my computer was not connected to the internet at the time I restarted.  My computer is a Macbook and I usually use it in a mobile environment, so I'm almost never connected to the internet when I reboot.

I like the product.  I've not had the slowdown issues I see posted here, in fact I was impressed by how fast it worked and how little CPU it used while running in the background, but until I can restart without problems, I'm afraid it will stay uninstalled.

FYI:  My computer is an '08 Macbook 13" aluminum with 4gb RAM, running OS X 10.6.4

:1000262


This thread was automatically locked due to age.
Parents
  • 0
    OleZimmer wrote:

    … maybe my "tests" were n´t robust enough …

    I don't doubt the robustness of anyone's tests :-)

    I could have put things better, sorry. I suppose what I want to say is that for this particular bug (requiring a forced restart or forced shutdown — after login to Mac OS X, and before the logging-in user can use the system) don't spend too much time trying to figure out what's going on. I have spent many hours trying to get perfectly reproducible steps to the bug, and trying to pinpoint the stage at which the bug bites, but the stage does vary significantly —

    • at worst, the computer stops responding after presenting the desktop background (no menu bar, no Dock, no trace of ~/Desktop files)
    • at best, the computer stops responding after presenting much more (the desktop background, partially populated menu bar, Dock, icons and maybe some previews of ~/Desktop files) 
    — and whilst I have a few hunches of factors that contribute to the bug, the steps to reproduce the bug for me boil down to 'after I install Sophos Anti-Virus, sooner or later, on my computer when I log in to my account that's protected by FileVault, the computer will stop responding before I can use it'. Steps like that are so vague that they'll be of little use to developers, heheh. 
     
    More detail to follow, maybe over an extended period. Watch this space :-)
     
    Nearly the bottom line for this post:
    troubleshooting this particular set of symptoms can be unexpectedly time consuming. Get into troubleshooting here only if you're perfectly happy with that loss of time, and a likelihood that what you're trying has already been tried. 
     
    The bottom line:
    the more people reproducing this bug, the merrier (for troubleshooting purposes) — in particular, I haven't tested in an (Apple supported) 64-bit kernel and extensions environment. 
    :1000639
Reply
  • 0
    OleZimmer wrote:

    … maybe my "tests" were n´t robust enough …

    I don't doubt the robustness of anyone's tests :-)

    I could have put things better, sorry. I suppose what I want to say is that for this particular bug (requiring a forced restart or forced shutdown — after login to Mac OS X, and before the logging-in user can use the system) don't spend too much time trying to figure out what's going on. I have spent many hours trying to get perfectly reproducible steps to the bug, and trying to pinpoint the stage at which the bug bites, but the stage does vary significantly —

    • at worst, the computer stops responding after presenting the desktop background (no menu bar, no Dock, no trace of ~/Desktop files)
    • at best, the computer stops responding after presenting much more (the desktop background, partially populated menu bar, Dock, icons and maybe some previews of ~/Desktop files) 
    — and whilst I have a few hunches of factors that contribute to the bug, the steps to reproduce the bug for me boil down to 'after I install Sophos Anti-Virus, sooner or later, on my computer when I log in to my account that's protected by FileVault, the computer will stop responding before I can use it'. Steps like that are so vague that they'll be of little use to developers, heheh. 
     
    More detail to follow, maybe over an extended period. Watch this space :-)
     
    Nearly the bottom line for this post:
    troubleshooting this particular set of symptoms can be unexpectedly time consuming. Get into troubleshooting here only if you're perfectly happy with that loss of time, and a likelihood that what you're trying has already been tried. 
     
    The bottom line:
    the more people reproducing this bug, the merrier (for troubleshooting purposes) — in particular, I haven't tested in an (Apple supported) 64-bit kernel and extensions environment. 
    :1000639
Children
No Data
Cookie Information Banner