1.1.1 not working

[Steve]

I too am getting spontaneous crashes with identical thread info;

Code: [Select]

Thread 8 Crashed:
0   libobjc.A.dylib               0x00007fff88fdae90 objc_msgSend + 16
1   com.abyssoft.teleport         0x00000001000152c2 -[TPIncomingTransfer _receivedData:] + 244
2   com.abyssoft.teleport         0x0000000100020e23 -[TPTCPSecureSocket _receivedData:] + 564
etc...
iMac driving a 1st gen MBA - both with latest Lion and Teleport 1.1.1

I had several problems getting 1.1.1 to run in the first place and had to trash the two com.abyssoft.teleport.plist files in my library preference folder (note, hold down option key when selecting GO menu in Finder in order to get to your user library) and re-install the teleport preference pane on both computers. Now it occasionally crashes and pulls the icon out of the menu bar. Re-launches easily enough. I did have a very odd failure-to-return-cursor event a couple of weeks ago when the iMac stopped accepting any input to wake it from screen-saver. No idea if it was related, but I was using Teleport to work on my laptop when the iMac stopped taking input (bluetooth everything) - system logs didn't offer any clue either - had to hard re-boot.

[Steve]

Just wanted to note that after posting my previous comment I had that odd freeze event a couple of hours later. It may be associated with a kernel: IOSurface: buffer allocation size error (http://https://discussions.apple.com/thread/3216687?start=30&tstart=0) and nothing to do with Teleport. Current rumour has that as a Flash problem so probably unrelated.

[see3d]

Just wanted to chime in.  I was using 1.1.1 just fine since release.  In fact, it had stabilized most things for me.

Suddenly in the middle of using it this morning, I experienced the keyboard issue.

I can select the client computer with the mouse, but the keyboard doesn't seem to "follow."  Shortcut keys (cmd-tab) work, but direct at the host computer.  Nother appears or responds on the client computer.

I tried removing my preferences plist, but to no avail.  Basically not workable for me now.

I have the same problem with my two Mac Pros running Snow Leopard.  During the night I have an Automator program runs backups to Time Machine.  The next morning, is when the problem starts.  The only way to clear the problem is to restart both machines.  I have not found any other method of fixing the problem.  This is such a pain!