1.1.1 Crashes and other quirks

[theckman]

Greetings,

I just recently picked up a MacBook Air (13.3 Inch 1.6 GHz) running Apple OS X Lion.  I've been using it to control a 2009 iMac running Snow Leopard.  Both systems have the latest updates installed.

I've had a few issues with Teleport that make me have to keep a mouse hand for the machine that I am controlling.  On multiple occasions I've had Teleport do a few things that made me need to manually intervene.  The most common is teleportd simply dying on one, or both, systems.  Here are two crash reports when teleportd crashed almost simultaneously on both systems:

- http://paste.pocoo.org/show/QptDGeKJOiOXPDKhFPJw/ (System doing the control -- Lion)
- http://paste.pocoo.org/show/Hm4t68OJchnchsjIDtoc/ (System being controlled -- Snow Leopard)

At this time I was simply using the system and nothing doing anything too insane.  I do also get a bunch of errors on the controlling system's (Lion) console:

"teleportd: unrecognized type is 30"

The other symptoms I have is that sometimes I have two cursors on both systems.  This only happens while I am controlling the shared Mac.  The local cursor isn't able to focus on anything (clicks, drags, etc. don't work) but it still moves.  The only way to get it to disappear is to bring the cursor back to the controlling system and then move it back to the shared system.

There's also cases where I need to issue the command to forcefully bring the cursor back.  The shared system seems to no longer be receiving my commands and it doesn't automatically bring it back to the controlling system.

Jul, have you thought about the possibility of releasing Teleport as an OpenSource application?  Placing the project on GitHub could gather more attention as well as become a catalyst for further development and features.  By placing it on GitHub you, and some other developers, could maintain the project as well as accept patches from other devs.

Thank you for Teleport.  It's an awesome tool.  I just wish I could rely on it to be consistent during my every day use.  Looking forward to 1.1.2  :mrgreen:

-Tim

[EliW]

I too am having the issue of the 'two mice pointers'.  Where the controlling machine will just start showing the mouse as well as the controlled machine.  Harmless, but very annoying.  And as said, the only way it seems to be able to pull that back ... is to flip the mouse over to the other monitor, then back again.

I've also had the ''joy" of the lockups.  Thing is when I've had the lockups so far, it seems to that the keycommands to pull the mouse back, don't do any good.   My mouse is showing only on the controlling mac, but the menu bar doesn't show 'controlling X' at all.   And basically I have no option but to hard shut down the machine.  Because no keyboard/mouse is working on it.  Rather 'harsh' really.

[theckman]

I too am having the issue of the 'two mice pointers'.  Where the controlling machine will just start showing the mouse as well as the controlled machine.  Harmless, but very annoying.  And as said, the only way it seems to be able to pull that back ... is to flip the mouse over to the other monitor, then back again.

I've also had the ''joy" of the lockups.  Thing is when I've had the lockups so far, it seems to that the keycommands to pull the mouse back, don't do any good.   My mouse is showing only on the controlling mac, but the menu bar doesn't show 'controlling X' at all.   And basically I have no option but to hard shut down the machine.  Because no keyboard/mouse is working on it.  Rather 'harsh' really.

Sometimes I've been lucky where the lockup happens when the mouse is back on the controlling PC.  The other end solves itself and then it starts working again.  Sometimes it happens and it flings the mouse back.  However, within the last 8 hours I've had the system get stuck with the need to power it down.  Luckily the MacBook Air boots quickly.

I really wish this would be open sourced...

[miramusic]

I have had the same thing happen recently and have had to hard reboot my Snow Leopard machine as the mouse pointer just moves and I cannot click on anything or use any key commands.

This is such an awesome piece of software that I use everyday however I have to stop using it now. It takes too long for my system to reboot and then my other software to start up.

I really hope this problem gets sorted out as soon as possible.

My systems:
Mac Pro 2.8 Intel Xeon running 10.6.8 which is ALWAYS the controller for
Mac Book Pro 2.2 Core 2 Duo running 10.7.3

Thanks.

-A

[jorisx]

Same here,

controller mac (iMac) stopped responding with the macbookpro, mouse was moving on the iMac but no other commands could be done, disconnecting/reconnecting bluetooth and keyboard didn't work
had to hard-rebooot the iMac.... :-/

running with:
iMac() always the controller
macbookpro (2.8ghz core 2 duo, 8gb)

[chollandjr]

appear to be having the same crash... Mountain Lion Preview 3 --> SnowLeopard.
Found this solution when Synergy stopped working during my testing with Preview 2. Teleport was PERFECT on preview 2. Installed Preview 3 this morning, and bingo... SnowLeopard side crashes consistently. No crash on Mtn Lion side.

Removed and reinstalled on both sides several times, re-authenticated the two with encryption, etc.
Flipped the connection SnowLeopard --> Mtn Lion... works fine. I simply can't work this way because I lose all my gestures on the trackpad which I have grown so accustomed to. :-(

Crash report from SnowLeopard:
Process:         teleportd [1210]
Path:            /Users/cholland/Library/PreferencePanes/teleport.prefPane/Contents/Resources/teleportd.app/Contents/MacOS/teleportd
Identifier:      com.abyssoft.teleport
Version:          (1069)
Code Type:       X86-64 (Native)
Parent Process:  launchd [414]

Date/Time:       2012-04-23 13:52:42.185 -0400
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Application Specific Information:
*** error for object 0x11300b468: incorrect checksum for freed object - object was probably modified after being freed.
 

[nphase]

Got similar problems as well. Mouse seems to send commands just fine but keyboard just stops functioning altogether on the slave, with the master making an error beep noise thing whenever i hit the keyboard while my mouse is on the slave. I've had this problem pre 1.1/1.1.1 as well, have only been able to solve it by rebooting both the slave and the master. Would love to have a patch for it, but been waiting for it for a while - currently looking for teleport alternative instead.

[nghtstr]

I have been having some odd issues.  Some of which have already been described here, but I figure why not just list them all.

• Sometimes the cursor/keyboard lags tremendously on the Slave machine, to the point where the mouse jumps from point to point on the slave, and the keyboard spews off 30 or so characters in a bunch to the Slave (no, I am not that fast of a typer)
• Sometimes the Master will lose connection with the Slave machine.
• Sometimes the Master or the Slave will completely drop the Teleport daemon.  I will have to re-activate it

Both machines are running on a Wireless network: Ran by an Airport Extreme (Dual Channel), on Wireless-N, all of a few feet away from each other.