Mac mini startup/ shutdown code?

What causes mac mini to display startup and shutdown code?

To shut-down your computer your can type "sudo halt" into Terminal.

Similar Messages

  • Mac Mini AHT error code:  2MLB/10/4: $0004.89f1

    Have Mac Mini G4 1.42 purchased in 2005, upgraded by Apple service center to 1 Gb and never used - sat in box. I recently starting using it after putting and experienced random kernel panics and application crashes. Ran AHT which produced error code on second pass: 2MLB/10/4: $0004.89f1 .
    Thinking this was RAM, replaced RAM with quality 1 Gb stick, ran AHT again, but on third pass received same error code, 2MLB/10/4: $0004.89f1 .
    I am interested in knowing EXACTLY what this error code means - cannot believe this is not online anywhere. Can anyone with an error code listing tell me? I already suspect this machine will become a paperweight.
    If so please post and/or email scotsilv AT aol.com
    Thanks
    Scot

    ...I noted that my machine's Boot ROM Version is: 4.8.9f1
    So, $0004.89f1 is simply the boot rom version and 10/4 the OS.
    Appears I had a loose Airport card, which when tightened seems to have made the machine stable.

  • Mac Mini startup issue

    So, earlier tonight, my computer was acting a little strange (it seems to have been flaky after updating to 10.4.8 lately) and after restarting, I get the gray apple screen, and the spinning indicator, but nothing else happens, other than more spinning. I've tried to boot from CD, or in safe mode, or open firmware, even, but nothing happens. I have a feeling that this is because I'm not using an Apple keyboard, but a logitech one. So I guess I really kind of have two questions, namely-what can I do to force a boot from a CD in this case, and, afterwards, what do you suggest I do to fix my computer? Do I need to reinstall the OS, or just repair disk permissions? Any help on this would be appreciated.

    I have the same exact issue! I have also tried everything. I have a Intel 1.66 GHz core duo Mac Mini (refurbished) using a Mac Keyboard and still nothing happens.
    My wife told me that it went into some kind of programing code and she thought it was a virus... ACK! and rebooted it. This is when the problem began.
    I have tried using the keys to safe boot and boot from the OS X disk to no avail. The only thing that works is holding the option key down and it show the MacHD icon. I can't get past that. I have tried to use my external hard drive to boot to, but it doesn't recognize it.
    I recently used software update to install the latest patches from Apple. It was running fine for a few days until this happened.
    Dual 533 MHz DA PPC G4   Mac OS X (10.4.8)   1.5 GB SDRAM, GeForce FX 5200

  • Mac Mini startup - battery (?) symbol on screen

    Trying to set up a Mac Mini for the first time. Followed instructions to the letter. Turned it on and the first screen is a diagram of something rectangular and vertical, with a pullout circle enlarging something that looks like maybe a battery (it's green) with an arrow pointing up. I have no clue what it's trying to tell me. Setup doesn't seem to be that complicated and this is not my first Mac. Any ideas before I call or head to the Genius Bar?

    Greetings, and welcome to the BlackBerry.com Support Forums.
    The device does not recognize the battery.
    Leave the device to charge 2-3 hours, and then, still connected to the USB cable, remove the the battery from the device a few seconds and reinsert it. If it boots--leave it to charge to 100% (check Options > Status for the percentage).
    If it doesn't boot--try using a wall outlet charger if you are not. If you are connected via USB to the PC, make certain that you have Desktop Manager (or the USB device drivers) installed, which you can download below.
    Make certain your USB cable is connected to one of the PC's main rear USB ports. Not a USB hub, nor a monitor USB port, nor a USB port on the front of the PC.
    Download Desktop Manager from here:
    https://www.blackberry.com/Downloads/entry.do?code​=A8BAA56554F96369AB93E4F3BB068C22
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Mac Mini Startup Disk

    Hi,
    I have just got a Mac Mini, Dual Core and am trying to startup from a firewire HDD just as I seem able to do on my Powerbook G4 1.5 GHz and Powermac G4 533 MHz. I have OS 10.4.8 installed on the Firewire HDD yet when I select 'Startup Disk' from System Preferences I do not see the OS on the firewire dirve as an option. Any help/suggestions would be very gratefully received. Thanks very much.
    Mac Mini 1.83 GHz Intel Core Duo   Mac OS X (10.4.9)  

    Hello! Your issue probably is related to the version of OSX you're trying to boot from. If the external is the exact same OS that's on the Mini it will work but if the OS is one for the PB or the G4 it's not likely to work. Take the Mini disk and do a new install on an external drive and you should have no problems or if you like you can "clone" the Mini drive to the external and it will work also. Tom

  • Dead Mac Mini - Startup Problems and more

    I have a 1.33 GHz Mac Mini with a bad hard drive that is causing me considerable grief trying to troubleshoot.
    When I first received the Mac Mini to look at (it belongs to my wife's Grandmother) the machine would chime and display the flashing folder on the screen indicating a missing system folder. I was not able to boot into single user mode so I booted first from a Tiger install DVD which worked fine. Disk Utility could see the drive but not repair it. Then I tried a Diskwarrior 4 CD which booted fine but again, was unable to repair the drive. Not wanting to give up just yet I took the Mini home and connected it to my intel iMac with Firewire. I did this several times and tried a variety of disk utilities that I have. However, eventually, the Mini would refuse to be recognized on the iMac. I had a monitor hooked up to it and saw that it was definitely going into target disk mode but I could not get the iMac to see it, even with swapping cables and holding my mouth just right.
    Eventually I gave up on the thought of recovering data and was reserved to attempt to reinitialize the drive to see if the drive would work. I tried booting off a Leopard install DVD. It would startup with the grey screen and apple logo and spinning icon but after about a minute the CD activity would stop and the apple logo would be replaced by a circle with a line through it. What does this mean? Thinking that maybe the CD was bad I tried a Tiger Install DVD I had and got the same result. I now find that whereas before I could boot off various CD's I now find that it will not boot off ANY of my CD's. After about a minute the CD noise stops and the machine just sits there, not hung but not progressing. I have tried leaving the machine for over 1/2 an hour and nothing.
    What could be wrong? Is there some point in the CD boot process where the hard drive is accessed and if the hard drive is toast will it cause the hang? Same with the Firewire Target mode? Should I crack this thing open and remove the hard drive and see if that fixes it or is the logic board toast?

    Have you tried the Apple hardware test? Assuming the CD drive will work, find the OS X discs that came with the mini, which in small print on the label says AHT Version x.x (should be the first OS X disc). Insert it and reboot holding the option key down. Choose the Apple hardware test, click the arrow pointing to the right, and follow directions. Choose the extended test. Does that give you any additional information?

  • Mac mini startup

    I had t replace my old mac mini when it crashed in October with a new mac mini.. Everything was running fine until last night when I performed a routine software update. After the update was complete, the computer did not restart/ask to restart like it usually does. My dock and my bar at the top of the screen disappeared so I had no choice but to turn the computer off manually by pressing and holding the power button. This morning I tried to turn it back on and the startup assistant appeared as if I was turning the computer on for the first time. I went through it anyway and when I clicked the Done button, it took me back to the first page of the startup assistant again!! I don't know what to do..

    my mom just called me having this exact same issue. she's 3 hours away so i'm hoping for a walk-through-able solution. she has the lower model intel mac mini, and she said she had just performed whatever the recommended updates were. she does them regularly, so it was what was posted within the last week. any help is greatly appreciated.
    -alex.

  • Mac mini startup problem. Blank desktop - no dock/icons.

    But i can see the clock, wifi symbol, etc.... and i can move the cursor.

    In Target mode what shows on the problems Mini's screen?
    This does not make sense?
    Its an intel G4 - i think 2011 model
    How to identify Mac mini models
    Also:
    http://en.wikipedia.org/wiki/Mac_Mini

  • How often needs Mac Mini a shutdown?

    After a while, Mac Mini (OS Lion installed) gets  sluggish.
    Shutting off is then necessar; when I restart, it works noramlly but already after a few hours I notice it is not so fresh.
    After some days it is impossible to work with.
    Shutting down is not easy. If you click the Shut Down under the Apple icon. It is tedious
    It is better to first force quit all programs
    Is there another way to quickly shut down ?
    Is there a speed up without shut down ?without  tedious procedures

    The "Eject" key is at the upper right corner of the keyboard.

  • Mac mini startup problems

    My Mac mini usually runs fine, when Im done using it I put it to sleep, when I need it I tap any key on the keyboard and it
    usually wakes up.  I have noticed that when we watch videos that are downloaded on the computer with Quicktime Player
    that the computer does not wake up with a tap on the keyboard.  I have to press the power button on the mac mini to get it to start,
    I have a grey screen, with the icons still visible and a power up indicator.  It takes about 10 seconds to get the screen back to normal.
    I have plenty of free space in memory 966.09 free of 999.35.  Any idea what is causing this problem?  Should I be concerned? If yes,
    how do I fix it?
    Mac mini  OS X 10.9.5   processor 2.3 GHz   Intel Core i7
    Memory 4 GB 1600MHz  DDR3
    Thanks,   Richard

    Hey 8149,
    Based on your description of the waking sequence when this happens (grey screen, power up indicator, can't wake from keyboard), it sounds like your Mac mini is entering Safe Sleep, which can be perfectly normal if the machine has been idle for a while. You may find the information in the following article helpful:
    OS X: Saving energy with Sleep - Apple Support
    Cheers,
    - Brenden

  • Mac mini startup disk full?

    I keep getting an error that says that my startup disk is full and it pauses open browsers and programs. What is this?

    Means you have no free space left on your hard drive. You can check this by selecting the disk's Desktop icon, then Press COMMAND-I to open the Get Info window. At the top you will see information on the disk drive's capacity, space used, and space available.
    When you get such an alert either you need to erase some of your files to free up space or replace the drive with a larger one.
    Visit The XLab FAQs and read the FAQ on freeing up space on your drive.

  • Mac Mini Experiencing Hard Freeze 3-4 Times Per day...

    About 10 days ago, my mid-2011 Mac Mini started experiencing a hard freeze wherein I would get the spinning beachball and slowly each open app would be come unresponsive and my only resort was to hold down the power button to restart.  Upon reboot, the system would work fine for about an hour then the freeze would start again.  I've rolled back my configuration to a state prior to the freezing, and in desperation, have done a completely clean re-install of the OS.
    System specs:
    Mid-2011 Mac Mini 2.7 GHz Core i7
    16 GB RAM
    256GB SSD
    750GB HDD
    Attached to a 27" LED Cinema Display, and an Airport Extreme Basestation/TimeCapsule (TimeMachine temporarily disabled)
    I've been reading the logs, but don't really know how to interpret them so I've included a a number of postings right up until I force the reboot.
    Thanks in advance!
    Log below: The system performs fine until 12:15 or so
    Sep  6 12:03:56 Kriss-Mac-mini.local WindowServer[94]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    Sep  6 12:04:05 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Sep  6 12:04:05 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Sep  6 12:04:27 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04eb0
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04f40
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04fd0
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba05090
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfbc0
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfc50
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfce0
    Sep  6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04e20
    Sep  6 12:06:44 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Sep  6 12:06:44 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Sep  6 12:06:55 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 12:07:38 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Sep  6 12:07:38 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Sep  6 12:07:49 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 12:08:36 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Sep  6 12:08:36 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Sep  6 12:08:47 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 12:09:33 Kriss-Mac-mini.local com.apple.qtkitserver[759]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
    Sep  6 12:09:33 Kriss-Mac-mini.local com.apple.qtkitserver[759]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
    Sep  6 12:09:33 Kriss-Mac-mini kernel[0]: Sandbox: sandboxd(769) deny mach-lookup com.apple.coresymbolicationd
    Sep  6 12:09:35 Kriss-Mac-mini.local sandboxd[769] ([759]): com.apple.qtkits(759) deny mach-lookup com.apple.printtool.agent
    Sep  6 12:10:15 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGAffineTransformInvert: singular matrix.
    Sep  6 12:10:15 --- last message repeated 3 times ---
    Sep  6 12:10:15 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
    Sep  6 12:10:25 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Sep  6 12:10:25 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Sep  6 12:11:00 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[776]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:11:01 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 12:11:09 Kriss-Mac-mini.local WindowServer[94]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    Sep  6 12:11:15 --- last message repeated 1 time ---
    Sep  6 12:11:15 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[782]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:11:24 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGAffineTransformInvert: singular matrix.
    Sep  6 12:11:24 --- last message repeated 1 time ---
    Sep  6 12:11:24 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
    Sep  6 12:11:47 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[786]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:12:35 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
    Sep  6 12:12:58 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[790]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:13:06 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
    Sep  6 12:13:10 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[794]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:15:12 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[806]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:15:22 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[809]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:15:51 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[816]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:16:07 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[818]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:17:10 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[823]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:17:24 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[825]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:18:22 Kriss-Mac-mini.local Locum[829]: Connection with distnoted server was invalidated
    Sep  6 12:19:05 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Sep  6 12:19:05 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[766]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:19:05 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Sep  6 12:20:01 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[844]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
    Sep  6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[845]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
    Sep  6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[844]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
    Sep  6 12:23:56 Kriss-Mac-mini.local Google Chrome Helper[845]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
    Sep  6 12:23:58 Kriss-Mac-mini.local Google Chrome Helper[847]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
    Sep  6 12:23:59 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[835]): Exit timeout elapsed (20 seconds). Killing
    Sep  6 12:24:01 Kriss-Mac-mini.local Google Chrome Helper[847]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
    Sep  6 12:24:01 Kriss-Mac-mini.local Google Chrome Helper EH[848]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
    Sep  6 12:27:54 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
    Sep  6 12:27:54 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
    Sep  6 12:28:45 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _handle_timer heartbeat detected detach for device 0xc-10.0.1.117:0!
    Sep  6 12:28:52 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: moduleFromLegacyDefaults: <ScreenSaverDefaults: 0x7fc57321f5a0>
    Sep  6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: Attempted search for modules of unknown type (4)
    Sep  6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
    Sep  6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
    Sep  6 12:49:01 Kriss-Mac-mini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=891[GoogleSoftwareUp] clearing CS_VALID

    I looked these up and none of the network profiles list these MAC addresses. Strange.
    I went to dinner and when I returned the computer was frozen again.  These strange entries appeared in the log:
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d657190
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d62bb70
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6570c0
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x100e6f130
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d680450
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d63b650
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6804e0
    Sep  6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6805a0
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5edd40
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c517540
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009b1150
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5d2120
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5de420
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c51e650
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10cd8b020
    Sep  6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10cdfb8f0
    Sep  6 15:57:58 Kriss-Mac-mini.local Dock[128]: CGSSetWindowTransformAtPlacement: Singular matrix [inf 0.000 0.000 inf]
    Sep  6 15:58:00 Kriss-Mac-mini.local Dock[128]: Unable to open IOHIDSystem (e00002bd)
    Sep  6 15:58:00 Kriss-Mac-mini kernel[0]: virtual bool IOHIDEventSystemUserClient::initWithTask(task_t, void *, UInt32): Client task not privileged to open IOHIDSystem for mapping memory (e00002c1)
    Sep  6 16:02:35 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff75469180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
    Sep  6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: Created shield window 0xdf for display 0x0424faa4
    Sep  6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
    Sep  6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
    Sep  6 16:03:50 Kriss-Mac-mini kernel[0]: PM notification cancel (pid 322, Transmit)
    Sep  6 16:03:50 Kriss-Mac-mini kernel[0]: IOPMrootDomain: idle cancel
    Sep  6 16:06:17 Kriss-Mac-mini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=352[GoogleSoftwareUp] clearing CS_VALID
    Then I rebooted.  Curious about the screenshot entry.  I'm stumped.

  • After installing win7 in bootcamp mac mini start only in windows

    I did install win 7 Home edition premium on my mac mini the same way as I did on my iMac.
    After the install I could booth Win7 but there was no bootcamp icon and it would always boot in win7.
    No way to go back to Mac OS whatever key press I tried. And there was no bootcamp.exe.
    As I am unning Lion and there i no DVD I installed bootcamp in Windows using the leopard DVD.
    After restart it came back to Win7 and now the bootcamp icon was there. THrough teh bootcamp
    icon i was able to restart in Mac OSX. From there I checked the harddrive and no error was reported.
    I then when to bootcamp and set it to restart in Mac OSX. It did restart but didn't boot at all. Just get
    the beep and that's it.
    Nothing helps: option, D, Shift, P&R,...
    I had a problem before that the Mac Mini would shutdown with no reason and no warning at random
    times. I brought it to the Apple store and they allegedly repaired it. Could this be related?
    I have other Mac mini (Intel) older and  also the previous version with the DVD as well as a Mac Book Pro
    and an iMac with excatly the same  configuration and never had any problem.
    I need help thanks,

    yes, no luck there either.
    Now I cannot boot at all.
    I never had a problem wih the Mac OSX side only that  crappy microsoft software. Unfortunately
    there are a lot of woftware that I need for my work that only exist under micorsoft.

  • Bluetooth Error on early 1.66Ghz Core Duo Mac Mini model.

    Something really weird that wasn't really happening until a couple weeks ago... I can connect to a bluetooth enabled cell phone just fine... I can even transfer some small files back and forth okay, BUT... if I attempt to transfer something big, like a music file... a 3MB mp3 per say... it will start the transfer and after a few seconds, sometimes longer... the error comes "The Hardware bluetooth is no longer available" ...
    NO CLUE!!!
    Anybody around having the same problem or had maybe?
    Thanks a lot and PEACE!
    Gui.
    Mac Mini 1.66Ghz Code Duo, 160Gb SATA, 2Gb SODDIM   Mac OS X (10.4.8)  

    If this mini was bought new in May 2007 it is still under warranty, and you should contact Apple. If you have an Apple store in your area you can make an appointment at the Genius Bar and have it looked at. If not, then simply call Apple and describe the symptoms. If they can't walk you through a series of troubleshooting steps to identify and resolve the problem, they'll arrange for the system to be returned to them for service. You don't have to put up with a defective drive.
    On a broader note, it's not likely to be your media, as long as you are trying to use good quality blanks rather than a low-cost generic brand. You might try a good quality blank from a different manufacturer to check however.
    Also, you mention 'Disco' and 'Toast' - which implies you have installed alternative CD buring software on the system. Nothing wrong with that, but make sure these applications are properly compatible with your version of MacOS, and the system - particularly that they are Intel-native copies. A problem with third-party burning applications could cause the symptoms you describe.

  • Mac Mini 10.6.8 slow startup

    I have a mac mini with 2 gb ram running 10.6.8. Hard drive is 500gb with over half of that unused. Initial boot time first thing in the morning is slightly over a minute. It also starts programs pretty slow after that for about 30 minutes. Then it seems fine for the rest of the day for the most part.
    I have reset pram.
    Repaired permissions.
    Excluded programs that I don't need from the login items list.
    Placed console and activitiy monitor in the login items in order to see if anything stands out as soon as it is booted. Nothing stands out to me.
    Below is the console listing from that last restart. I am hoping that someone might see something here that would give a clue to the slow down.
    Any help greatly appreciated.
    10/3/12 9:42:33 AM
    com.apple.launchd.peruser.501[116]
    ([0x0-0x30030].com.apple.systemevents[303]) Exited: Killed
    10/3/12 9:42:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:42:33.087 - Debug
    - LMIGUIAgent - SessionManager - Application exiting
    10/3/12 9:42:33 AM
    com.apple.launchd.peruser.501[116]
    (com.apple.AirPortBaseStationAgent[141]) Exited: Killed
    10/3/12 9:42:33 AM
    com.apple.launchd.peruser.501[116]
    (com.apple.FolderActions.enabled[148]) Exited: Killed
    10/3/12 9:42:33 AM
    com.logmein.logmeinguiagent[142]
    Session - Error occured:read errno: (9) Bad file descriptor
    10/3/12 9:42:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:42:33.157 - Debug
    - LMIGUIAgent - SessionManager - Connection closed
    10/3/12 9:42:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:42:33.157 - Debug
    - LMIGUIAgent - SessionManager - Closing DisplayServer
    10/3/12 9:42:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:42:33.157 - Debug
    - LMIGUIAgent - SessionManager - DisplayServer close
    10/3/12 9:42:33 AM
    com.apple.launchd.peruser.501[116]
    ([0x0-0x1c01c].com.apple.ImageCaptureExtension2[181]) Exited: Killed
    10/3/12 9:42:33 AM
    MagicMenuHotKeyDaemon[195]
    Quit
    10/3/12 9:42:33 AM
    [0x0-0x14014].com.stuffit.MagicMenu[161]
    2012-10-03 09:42:33.243 MagicMenuHotKeyDaemon[195:60b] Quit
    10/3/12 9:42:46 AM
    com.apple.launchd[1]
    *** launchd[1] has started up. ***
    10/3/12 9:43:27 AM
    com.apple.SystemStarter[31]
    Starting HP IO Monitor
    10/3/12 9:43:27 AM
    com.apple.SystemStarter[31]
    Starting HP Trap Monitor
    10/3/12 9:43:27 AM
    com.apple.SystemStarter[31]
    /Library/StartupItems/HP Trap Monitor/HP Trap Monitor: line 15: /Library/Printers/hp/hpio/HPIO Trap Monitor.app/Contents/MacOS/HPIO Trap Monitor: No such file or directory
    10/3/12 9:43:28 AM
    com.apple.ReportCrash.Root[96]
    2012-10-03 09:43:28.969 ReportCrash[96:2a03] Saved crash report for hpdot4d[95] version ??? (???) to /Library/Logs/DiagnosticReports/hpdot4d_2012-10-03-094328_localhost.crash
    10/3/12 9:43:30 AM
    com.apple.launchd[1]
    (com.logmein.logmeinguiagentatlogin) Unknown key for boolean: UseLMILaunchAgentFixer
    10/3/12 9:43:30 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:30.501 - Info 
    - LMIGUIAgent - Main - starting...
    10/3/12 9:43:30 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:30.561 - Debug
    - LMIGUIAgent - GetCurrentSessionID() - Current SessionID is -1
    10/3/12 9:43:30 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:30.561 - Info 
    - LMIGUIAgent - Main - started:113 uid:0, sessionid:-1 (parent:1 launchd)
    10/3/12 9:43:30 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:30.561 - Info 
    - LMIGUIAgent - Main - checking window server connection
    10/3/12 9:43:30 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:30.563 - Info 
    - LMIGUIAgent - Main - checking window server session
    10/3/12 9:43:30 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:30.564 - Info 
    - LMIGUIAgent - Main - connecting to session manager
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.064 - Debug
    - LMIGUIAgent - SessionManager - init
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.069 - Info 
    - LMIGUIAgent - CSC - storeOriginalOutputDevice - stored outputDeviceID: 263
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.187 - Debug
    - LMIGUIAgent - SessionManager - SessionAgent Loaded
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.187 - Debug
    - LMIGUIAgent - SessionManager - SessionAgent Starting
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.188 - Debug
    - LMIGUIAgent - GetCurrentSessionID() - Current SessionID is 501
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.189 - Debug
    - LMIGUIAgent - GetCurrentSessionID() - Current SessionID is 501
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.190 - Debug
    - LMIGUIAgent - SessionManager - sessionStateChanged activated=1 sessionid=501 consoleuser=minimac IsAtActiveConsole=1 SessionIsLoggedIn=1 IsOnLoginScreen=0
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.190 - Debug
    - LMIGUIAgent - SessionManager - SessionAgent Started
    10/3/12 9:43:31 AM
    com.apple.launchctl.Aqua[121]
    launchctl: Please convert the following to launchd: /etc/mach_init_per_user.d/com.adobe.SwitchBoard.monitor.plist
    10/3/12 9:43:31 AM
    com.apple.launchd.peruser.501[119]
    (com.logmein.logmeingui) Unknown key for boolean: UseLMILaunchAgentFixer
    10/3/12 9:43:31 AM
    com.apple.launchd.peruser.501[119]
    (com.logmein.logmeinguiagent) Unknown key for boolean: UseLMILaunchAgentFixer
    10/3/12 9:43:31 AM
    com.apple.launchd.peruser.501[119]
    (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - Main - HandleSigterm.start, got signal 15
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - Main - SessionManagerConnection sessionTerminating
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - Main - SessionManagerConnection quit ([NSApplication sharedApplication] terminate)
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - Main - HandleSigterm.end
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - SessionManager - sessionTerminating
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - SessionManager - DisplayServer stop
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - SessionManager - DisplayServer close
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.570 - Debug
    - LMIGUIAgent - GUIAgent - DisplayServerStopped.Sent[113]
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.573 - Debug
    - LMIGUIAgent - SessionManager - Application exiting
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    Session - Error occured:read errno: (9) Bad file descriptor
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.574 - Debug
    - LMIGUIAgent - SessionManager - Connection closed
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.574 - Debug
    - LMIGUIAgent - SessionManager - Closing DisplayServer
    10/3/12 9:43:31 AM
    com.logmein.logmeinguiagentatlogin[113]
    2012-10-03 09:43:31.574 - Debug
    - LMIGUIAgent - SessionManager - DisplayServer close
    10/3/12 9:43:32 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:32.924 - Info 
    - LMIGUIAgent - Main - starting...
    10/3/12 9:43:32 AM
    com.apple.launchd.peruser.501[119]
    (com.apple.Kerberos.renew.plist[139]) Exited with exit code: 1
    10/3/12 9:43:33 AM
    LogMeInGUI[143]
    LogMeIn GUI started
    10/3/12 9:43:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:33.111 - Debug
    - LMIGUIAgent - GetCurrentSessionID() - Current SessionID is 501
    10/3/12 9:43:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:33.111 - Info 
    - LMIGUIAgent - Main - started:142 uid:501, sessionid:501 (parent:119 launchd)
    10/3/12 9:43:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:33.111 - Info 
    - LMIGUIAgent - Main - checking window server connection
    10/3/12 9:43:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:33.111 - Info 
    - LMIGUIAgent - Main - checking window server session
    10/3/12 9:43:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:33.112 - Info 
    - LMIGUIAgent - Main - connecting to session manager
    10/3/12 9:43:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:33.612 - Debug
    - LMIGUIAgent - SessionManager - init
    10/3/12 9:43:33 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:33.949 - Info 
    - LMIGUIAgent - CSC - storeOriginalOutputDevice - stored outputDeviceID: 263
    10/3/12 9:43:34 AM
    [0x0-0xc00c].iShockXDriver[156]
    iSXDSrc/ShockDevice.cpp:424: failed assertion `KERN_SUCCESS == ( kr = IOServiceOpen( enumer, mach_task_self(), kIOFBSharedConnectType, &fb) )'
    10/3/12 9:43:34 AM
    com.apple.launchd.peruser.501[119]
    (0x100203a10.mach_init.switchboard.sh) Failed to check-in!
    10/3/12 9:43:34 AM
    LMIGUIAgent[142]
    Could not connect the action buttonPressed: to target of class NSApplication
    10/3/12 9:43:34 AM
    LMIGUIAgent[142]
    Could not connect the action buttonPressed: to target of class NSApplication
    10/3/12 9:43:34 AM
    LMIGUIAgent[142]
    Could not connect the action buttonPressed: to target of class NSApplication
    10/3/12 9:43:34 AM
    LMIGUIAgent[142]
    Could not connect the action buttonPressed: to target of class NSApplication
    10/3/12 9:43:34 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:34.137 - Debug
    - LMIGUIAgent - SessionManager - SessionAgent Loaded
    10/3/12 9:43:34 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:34.137 - Debug
    - LMIGUIAgent - SessionManager - SessionAgent Starting
    10/3/12 9:43:34 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:34.144 - Debug
    - LMIGUIAgent - GetCurrentSessionID() - Current SessionID is 501
    10/3/12 9:43:34 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:34.148 - Debug
    - LMIGUIAgent - GetCurrentSessionID() - Current SessionID is 501
    10/3/12 9:43:34 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:34.148 - Debug
    - LMIGUIAgent - SessionManager - sessionStateChanged activated=1 sessionid=501 consoleuser=minimac IsAtActiveConsole=1 SessionIsLoggedIn=1 IsOnLoginScreen=0
    10/3/12 9:43:34 AM
    com.logmein.logmeinguiagent[142]
    2012-10-03 09:43:34.148 - Debug
    - LMIGUIAgent - SessionManager - SessionAgent Started
    10/3/12 9:43:36 AM
    com.apple.launchd.peruser.501[119]
    ([0x0-0xc00c].iShockXDriver[156]) Job appears to have crashed: Abort trap
    10/3/12 9:43:36 AM
    com.apple.WindowServer[99]
    Wed Oct  3 09:43:36 MacMini.local WindowServer[99] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    10/3/12 9:43:37 AM
    ReportCrash[168]
    Saved crash report for iShockXDriver[156] version 1.0.3 (1.0.3) to /Users/minimac/Library/Logs/DiagnosticReports/iShockXDriver_2012-10-03-094336_M acMini.crash
    10/3/12 9:43:37 AM
    LogMeInGUI[143]
    Config watcher thread started
    10/3/12 9:43:37 AM
    LogMeInGUI[143]
    String:RC:INACTIVE
    10/3/12 9:43:37 AM
    LogMeInGUI[143]
    remoteControl:INACTIVE
    10/3/12 9:43:37 AM
    LogMeInGUI[143]
    processLine:ACCESSMASK: 18446743936270597119
    10/3/12 9:43:38 AM
    LogMeInGUI[143]
    String:WEBSVC|ONLINE
    10/3/12 9:43:40 AM
    [0x0-0x15015].com.apple.systemevents[163]
    com.apple.FolderActions.enabled: Already loaded
    10/3/12 9:43:47 AM
    MagicMenuHotKeyDaemon[190]
    Started
    10/3/12 9:43:47 AM
    [0x0-0x14014].com.stuffit.MagicMenu[162]
    2012-10-03 09:43:47.134 MagicMenuHotKeyDaemon[190:60b] Started
    10/3/12 9:43:47 AM
    MagicMenuHotKeyDaemon[190]
    Started
    10/3/12 9:43:47 AM
    [0x0-0x14014].com.stuffit.MagicMenu[162]
    2012-10-03 09:43:47.134 MagicMenuHotKeyDaemon[190:60b] Started

    There seems to be a login item "com.logmein.logmeinguiagentatlogin" (which I can't identify) that is giving you a problem at login?
    Go to: Apple > System Preferences > Accounts > Login Items and see what programs that you have set to open at login.
    Example:
    First try removing one or two that seem suspect from the list and see if that helps. Then if that doesn't help, remove them all.
    Also keep in mind that some may reappear on there own at the next startup, if they do please let us know what they are.

Maybe you are looking for