I haven't had this happen in a long long time, so it's worth noting:
About an hour into the session last night, my first since the update, I got that fullscreen-client-freeze-of-doom. I still saw chat go by but could not chat or control my ship. No keyboard input whatsoever, could not force quit, had to power cycle (running Mac 10.7.4).

The truly inconvenient thing is that I had 3 people aboard my trident, and they all lost their ship and cargo when I disconnected (each had a Fused Composite Plate and 40-80cu of minerals, depending on the moth they were in). This begs the suggestion that ships aboard a player trident not be killed to home base if the trident pilot suffers a disconnect: one of the few ongoing useful tasks a player trident can perform is hauling large crafting parts both in hold and in docked ships. If docking with precious cargo is at the mercy of client stability, why risk it?

Another argument for persistent player cappies. Meanwhile, is it possible to eject docked ships if the trident disconnects?

I witnessed the loss of cargo and the disappointment of the victims affected. With issues like this, I grow concerned that TRI having a few Tridents at its disposal for transportation purposes is only going to result in us losing stuff and opening bugs. I really hope this is isolated and ultimately resolved soon, otherwise theres no point in investing effort into something that is inherently unreliable, much less establishing an entire business based on Trident usage.

If a host trident goes offline/dies, the passenger ships should be 'ejected' or kicked.. not destroyed.

If a trident is destroyed, I could understand the loss of docked ships, as they should get out by then, but currently in both scenarios, all cargo carried by ships aboard is lost. No chance to recover it. I'll post in suggestions about these issues, as they significantly crushes the spirit of cooperative play needed to operate a player cappie.

On the actual bug I'm reporting: I've since had another client freeze in the trident, tho without the keyboard lockout. I tried logging out and the timer kept adding 10 seconds for every 3 or 4 it counted down. Reloading the interface cleared that, but not the freeze (hung on warp-in animation this time). Before this last update, I've only had 1 disconnect in the trident in the 15 months it has been in service, and that was an interaction with MAID, which I no longer use.

It's freezing for me on login. Hangs endlessly on "Entering Station..." If I force quit (I'm on a Mac) and restart VO, after several tries, I'll finally get the station, but if I undock, attempting to redock will freeze the client again.

It's clear from the music that the server thinks you're docked, but the client isn't getting the message.

The game is completely unplayable at the moment.

oh, and BTW TRI: I can replace the FCP if the devs won't. But they ought to IMHO.

Thanks for the report.

Do you still have the problems when no plugins installed?

I'm testing combinations now. I'll let you know when I've figured how which ones (if any) may be causing the problems.

For my client, this appears now to be the result of a plugin built by one of my guildies. I'm in the process of rebuilding it now to avoid this problem.

How could plugins possibly cause other players to lose their ship and cargo?

He's talking about the freezing, not the capship stuff. Note the thread title ;)