My original posting was worded poorly. When I said HEADLESS, I really meant that it did not have a dedicated computer monitor attached. The mini is attached via an HDMI cable to my A/V receiver, which is attached via an HDMI cable to my HDTV. So, for most of the day, the mini is headless in the sense that the A/V receiver and the HDTV are turned off (though the mini is usually left running).
In a typical setting, where a mini might be connected to a dedicated computer monitor, would there be a problem if the display were turned off when not in use? I would not expect that to be a problem. This situation seems analogous, though perhaps the HDMI connection introduces new factors that create a problem. I suppose that in the usual setting of mini plus dedicated monitor, I would turn on the monitor before turning on the mini, whereas in this case I leave the mini on (and try to access it remotely through screen sharing) even though the "monitor" (i.e., the HDTV/receiver combo) is off. Should that matter? It seems like that is a "headless" situation. Gregg On 9 Sep 2011, at 4:04 PM, Macs R We wrote: > Don't I remember you saying in your original posting that you ran this mini > HEADLESS? That would explain all the console messages. It can't get the > display bounds of a nonexistent display. And I'm sure it has a direct > bearing on your Mini's fickle behavior when it comes to magically changing > its screen sizes for screen sharing/VNC. > > On Sep 9, 2011, at 6:58 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote: > >> On Sep 9, 2011, at 1:07 AM, LuKreme wrote: >> >> "Dinse, Gregg (NIH/NIEHS) [E]" >> <[email protected]<mailto:[email protected]>> squawked out on Thursday >> 08-Sep-2011@08:20:55 >> Why doesn't the mini just keep a resolution until I change it? The >> resolution keeps changing on its own. Is this some weird HDMI handshaking >> issue? The HDTV is turned on and off much more often than I access the mini. >> >> Interesting. I have a mini hooked up via HDMI->DVI to a monitor and it’s >> never changed resolution. 1920x1050. I would have to suspect the TV or the >> turning on/off the TV is the issue. >> >> I don't know if the screen resolution problem is related to the mini >> freezing problem, but I am attaching a section of the Apple System Log >> message file. I don't know how to interpret the results, but I see the word >> "error" multiple times, as well as the phrase "This is probably going to >> crash sometimes". >> >> Do I have bad hardware? The only change I made was to replace the original >> 2-GB of RAM with 8-GB of Kingston RAM. >> >> Is the OS corrupted? Should I just reinstall? >> >> Thanks in advance for any help you can give me. >> >> Gregg >> >> ==================== >> >> 2011-08-30 00:17:20 -0400 ScreenSaverEngine[1038]: init [1286]: invalid >> framebuffer operation >> 2011-08-30 00:17:20 -0400 ScreenSaverEngine[1038]: reshape [1286]: invalid >> framebuffer operation >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-08-30 00:19:26 -0400 Finder[145]: _NXGetScreenRect: error getting >> display bounds (1001) >> 2011-09-01 22:47:16 -0400 SubmitDiagInfo[2047]: Could not write whitelist! >> Error Domain=NSCocoaErrorDomain Code=513 "You don‚Äôt have permission to >> save the file ‚ÄúSubmitDiagInfo.domains‚Äù in the folder >> ‚ÄúCrashReporter‚Äù." UserInfo=0x7fdf72217370 >> {NSFilePath=/Library/Application >> Support/CrashReporter/SubmitDiagInfo.domains, NSUserStringVariant=Folder, >> NSUnderlyingError=0x7fdf7221cb60 "The operation couldn‚Äôt be completed. >> Permission denied"} >> 2011-09-01 22:54:24 -0400 SoftwareUpdateCheck[2836]: SoftwareUpdateCheck >> (Launch): non-admin user >> 2011-09-01 22:54:24 -0400 com.apple.launchd.peruser.502[115]: Throttling >> respawn: Will start in 1500 seconds >> 2011-09-01 23:24:24 -0400 SoftwareUpdateCheck[2841]: SoftwareUpdateCheck >> (Launch): non-admin user >> 2011-09-01 23:24:24 -0400 com.apple.launchd.peruser.502[115]: Throttling >> respawn: Will start in 1500 seconds >> 2011-09-01 23:54:24 -0400 SoftwareUpdateCheck[2853]: SoftwareUpdateCheck >> (Launch): non-admin user >> 2011-09-01 23:54:24 -0400 com.apple.launchd.peruser.502[115]: Throttling >> respawn: Will start in 1500 seconds >> 2011-09-02 00:24:33 -0400 SoftwareUpdateCheck[2856]: SoftwareUpdateCheck >> (Launch): non-admin user >> 2011-09-02 00:24:33 -0400 com.apple.launchd.peruser.502[115]: Throttling >> respawn: Will start in 1496 seconds >> 2011-09-03 08:53:23 -0400 SoftwareUpdateCheck[2988]: SoftwareUpdateCheck >> (Launch): non-admin user >> 2011-09-03 08:53:23 -0400 com.apple.launchd.peruser.502[115]: Throttling >> respawn: Will start in 1500 seconds >> 2011-09-03 17:57:37 -0400 Software Update[3167]: Layout still needs update >> after calling -[WebHTMLView layout]. WebHTMLView or one of its superclasses >> may have overridden -layout without calling super. Or, something may have >> dirtied layout in the middle of updating it. Both are programming errors in >> Cocoa Autolayout. The former is pretty likely to arise if some pre-Cocoa >> Autolayout class had a method called layout, but it should be fixed. >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: Looking for applications at >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: --(null) >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: Path PurpleRestore.app given to >> -[NSWorkspace iconForFile:] is not a full path. >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: img:1 >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: >> timerMethod >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: >> updateTable >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: >> applicationShouldTerminate >> 2011-09-03 17:57:52 -0400 AlertAll[4229]: >> applicationWillTerminate >> 2011-09-03 17:57:55 -0400 com.apple.launchd.peruser.502[115]: Exited with >> code: 1 >> 2011-09-03 18:01:05 -0400 loginwindow[62]: NSAlert is being used from a >> background thread, which is not safe. This is probably going to crash >> sometimes. Break on _NSAlertWarnUnsafeBackgroundThreadUsage to debug. This >> will be logged only once. This may break in the future. >> 2011-09-03 18:01:13 -0400 com.apple.launchd.peruser.502[115]: Exited: >> Killed: 9 >> 2011-09-03 18:01:13 -0400 com.apple.launchd.peruser.502[115]: Exited: >> Killed: 9 >> 2011-09-03 18:01:13 -0400 com.apple.launchd.peruser.502[115]: Exited: >> Killed: 9 >> 2011-09-03 18:01:13 -0400 com.apple.launchd.peruser.502[115]: Exited: >> Terminated: 15 >> 2011-09-03 18:01:13 -0400 com.apple.launchd.peruser.502[115]: Exited: >> Killed: 9 >> 2011-09-03 18:01:13 -0400 com.apple.dock.extra[5380]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:01:13 -0400 com.apple.dock.extra[5380]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:01:13 -0400 com.apple.dock.extra[5380]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:01:13 -0400 com.apple.dock.extra[5380]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:03:08 -0400 com.apple.launchd.peruser.502[114]: Unknown key >> for boolean: DisallowDataExecute >> 2011-09-03 18:03:08 -0400 com.apple.launchd.peruser.502[114]: Falling back >> to default Mach exception handler. Could not find: com.apple.ReportCrash.Self >> 2011-09-03 18:03:10 -0400 com.apple.dock.extra[170]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:03:10 -0400 com.apple.dock.extra[170]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:03:10 -0400 com.apple.dock.extra[170]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:03:10 -0400 com.apple.dock.extra[170]: Could not connect the >> action buttonPressed: to target of class NSApplication >> 2011-09-03 18:03:17 -0400 talagent[154]: >> CGSConnectionRelinquishWindowRights(cid, newWindowNumber, reservedRights): >> CGError 1001 on line 602 >> 2011-09-03 18:03:28 -0400 talagent[154]: >> CGSConnectionRelinquishWindowRights(cid, newWindowNumber, reservedRights): >> CGError 1001 on line 602 >> 2011-09-03 18:03:45 -0400 Bluetooth Setup Assistant[195]: initiateDeviceSetup >> 2011-09-03 18:03:50 -0400 Bluetooth Setup Assistant[195]: >> readHIDEmulationDevice: HID emulation device found: dinse‚Äôs mouse >> 2011-09-03 18:03:50 -0400 Bluetooth Setup Assistant[195]: >> readHIDEmulationDevicesComplete: error: 0 >> 2011-09-03 18:03:50 -0400 Bluetooth Setup Assistant[195]: >> startAutomaticDeviceSetup >> 2011-09-03 18:03:50 -0400 Bluetooth Setup Assistant[195]: >> stopAutomaticDeviceSetup >> 2011-09-03 18:03:50 -0400 Bluetooth Setup Assistant[195]: >> automaticDeviceSetupStarted >> 2011-09-03 18:04:31 -0400 com.apple.systemprofiler[209]: 2011-09-03 >> 18:04:31.529 system_profiler[225:60b] Internal name did not resolve to >> internal address! >> 2011-09-03 18:16:42 -0400 System Preferences[426]: /usr/sbin/nvram boot-args >> (exit status 1) >> 2011-09-03 18:16:42 -0400 System Preferences[426]: /usr/sbin/nvram boot-args >> (exit status 1) >> 2011-09-03 18:16:42 -0400 System Preferences[426]: willDeauthenticate: (null) >> 2011-09-03 18:16:43 -0400 System Preferences[426]: currentBootDevice: being >> checked by DiskManagement _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
