I think I may have found a bug with the LMIRescue.pkg which affects Mac OS X 10.6 and above.
I have experienced this issue on Macs running Snow Leopard and Lion (but haven't tested on Leopard).
The problem occurs after downloading the LMIRescue.pkg(.zip) and following the usual installation screens, the Recue console doesn't start up - and there's no error message.
Despite repeated attempts to re-install and reboot, the normal automatic start-up of the chat window never appears. The process for LMIR wasn't running either.
After hunting around and checking the console messages. It turned out that a previous support session had extracted the LIMRescue package's temporary files into /tmp - under a different user. This resulted in permissions being set with the previous user as the owner (-rwxr-xr-x userA users).
As a result, when UserB logged in and tried to start a session, the files in /tmp couldn't be overwritten and the console failed to start.
Is there a way of forcing LMIRescue to clean up after the session?
I haven't come across this before as the problem only occurs when using more than one user profile and in my experience, I've only had to support Macs set up with a single user.
Is this a bug?
In case it's useful, here are some of the details of the session:
Session sent by Email via the LMI servers.
Remote Controlled started on Windows XP.
Client OSes with the issue - MacBook running OSX 10.6.8 and iMac running 10.7)
I guess to fix, I would either talk the user through deleting the contents of /tmp via a terminal (which would be tricky). Or alter the permissions on /tmp to rwx for everyone. But as there was no error indicating that LMI had a problem - it took checking for console error messages and quite bit of time to deduce that this was the problem.
