Remove annoying fatal_error() after wineserver crash

Alexandre Julliard julliard at
Tue Oct 9 18:15:46 CDT 2001

Malte Starostik <malte at> writes:

> not sure about the reason for that "the socket exists, but I can't connect" 
> message, but IMHO it's pretty annoying. I hit this fatal_exit() very often 
> while debugging reaktivate. And in such cases - or when starting an app from 
> a desktop / startmenu icon - when wine's STDERR goes to ~/.xsession-errors 
> instead of a shell, the user has no chance to figure why an app won't start. 
> Well, long story, short patch which Works for Me (TM) but I don't know if 
> there's anything wrong with doing this...

The problem with this is that it creates a race condition and we may
end up with two servers running in the same directory, which is bad.

The error message should only happen when a previous server has
crashed, which is a critical error (the server should never crash no
matter what the app does). In that case you should also have a core
file in the same directory as the socket, which you can use to debug
and fix the crash.

Alexandre Julliard
julliard at

More information about the wine-devel mailing list