Like the subject says: when there is an incoming connection, TeamViewer gets through the handshake, then TeamViewer_Desktop crashes. Relevant excerpt from the log:
Negotiating session encryption: client handshake received Negotiating session encryption: client handshake received Negotiating session encryption: server handshake sent, encryption established with AES key length 256 HandleSigChld: Child was dumped: 1744 signal 11 ProcessControlBase: Process 1744 in session **Please do not post TeamViewer IDs** has terminated
(1744 is the PID of TeamViewer_Desktop)
Brief history if it's relevant:
Let me know if it would help to post the logs, or core/stack dump. Please help me.
EDIT: It's also potentially noteworthy that this is somewhat of a headless server. I say somewhat, because I've stuck a couple of resistors in certain pinholes of the VGA port, so the computer thinks it' connected to a monitor and starts up X normally (or at least it did in 12.04).
UPDATE: So, I have gotten things to work, mostly, with the following work-around:
So, I think this is still a bug, since connections using Server Id crash. I would like to get this back to where I can use double-click to connect, but at least this gives me access for now.
EDIT: I just realized double-click still works. I just had to manually click "Connect using password" once, I guess... So, even though there's either a bug in TeamViewer or something wonky with my setup, I will mark this as the solution since it gets things working for me in the end.
EDIT2: Some of you may have realized my folly here... This only works if you open the TeamViewer GUI on the remote machine. So, this doesn't actually solve my problem, as I'm unable to connect after reboot. I need to be able to use the Server Id instead of the User Id.